LCS2016_075 < P1076

P1076 Web>VHDL2017>LCS2016_075 (2017-04-02, PatrickLehmann) (raw view)EditAttach
---+ Language Change Specification for closely-related record types

---++ Summary

| <sticky><b>LCS Number:</b></sticky> | LCS-2016-075 |
| <sticky><b>Version:</b></sticky>  | 1 |
| <sticky><b>Date:</b></sticky>  | 20-Dec-2016 |
| <sticky><b>Status:</b></sticky>  | In progress |
| <sticky><b>Author:</b></sticky>  | Ryan Hinton |
| <sticky><b>Email:</b></sticky>  | [[Main.RyanHinton]] |
| <sticky><b>Source Doc:</b></sticky> | [[RelatedRecords][Closely related record types]] |
| <sticky><b>Summary:</b></sticky>  | Add a definition of a closely-related record type so type conversions are possible. |

---+++ Voting Results: Cast your votes here

Yes:
   1 %USERSIG{RyanHinton - 2016-12-20}% - ver 1
   1 %USERSIG{PatrickLehmann - 2016-12-31}% - ver 1
   1 %USERSIG{MartinThompson- 2017-02-17}% Version 1
   1 %USERSIG{JimLewis- 2017-02-21}% Version 1
   1 %USERSIG{ThomasPreusser - 2017-02-23 }% - ver 1
   1 %USERSIG{MartinZabel - 2017-01-25}% - ver 1

No:

Abstain:
   1 %USERSIG{BrentHahoe - 2017-02-16}% Version 1 - Abstain due to lack of personal time for review.

---+++ Details of Language Change

Additions are in %RED%red font%ENDCOLOR%.  Deletions are %RED%<del>crossed out</del>%ENDCOLOR%. Editing notes are in %GREEN%green font%ENDCOLOR%.

---++++ Section 9.3.6 Type Conversions
---+++++ Page 137 (pdf 151) near the middle.

Explicit type conversions are allowed between closely related types. In particular, a type is closely related to itself. Other types are closely related only under the following conditions:
   * _Abstract numeric types_ -- Any abstract numeric type is closely related to any other abstract numeric type.
   * _Array types_ -- Two array types are closely related if and only if the types have the same dimensionality and the element types are closely related%RED%.%ENDCOLOR%
   * %RED% _Record types_ -- Two record types are closely related if and only if each element of the target type has a matching element (see 9.2.3) in the type of the operand, and the corresponding types for matching elements are closely related.%ENDCOLOR%

---+++++ Page 138 (pdf 152), third paragraph.

In a %RED%type or%ENDCOLOR% subtype conversion where the target type is a record type, the value of each element of the result is that of the matching element of the operand (see 9.2.3) converted to the subtype of the element of the result.

... %GREEN%(move to notes at the end of this section)%ENDCOLOR%

%RED%<del>NOTE 2--Two distinct record types are not closely related, even if they have the same element identifiers and element subtypes. A record type is, however, closely related to itself. Hence, an operand of a record type can be converted to a subtype of the record type.</del>%ENDCOLOR%  %GREEN%(The prohibitive part is no longer correct.  We can keep the permissive parts if someone thinks they still have value.)%ENDCOLOR%

-- Main.RyanHinton - 2016-12-20

---++ <a name="Comments"></a>Comments

To review the LCS, I need the whole text of the note you deleted.    
Some of your editing colors are off and it is hard to see that you are deleting the sub in front of subtype.

-- %BUBBLESIG{JimLewis - 2016-12-21}%

Colors improved, added more explanatory text.  I didn't bump the revision because there are no normative changes.

-- %BUBBLESIG{RyanHinton - 2016-12-21}%

It is only an editing note, but what is meant by: "(The second paragraph on this page describes record subtype conversions once a type conversion is defined for a record type.)"?

The 2nd paragraph on page 138 addresses arrays only, doesn't it?

-- %BUBBLESIG{MartinZabel - 2017-01-23}%

Good point.  It appears I may have been referring back to the text I just changed....  I've modified the text slightly to include type and subtype conversions.

-- %BUBBLESIG{RyanHinton - 2017-02-10}%

%COMMENT%
Topic revision: r13 - 2017-04-02 - 15:43:35 - PatrickLehmann
P1076