-
Key: DDSXTY14-64
-
Status: closed
-
Source: Real-Time Innovations ( Dr. Gerardo Pardo-Castellote, Ph.D.)
-
Summary:
The spec states that @key members are always "must understand" does this mean that when represented in a TypeObject the member should also have the "must understand" flag set or is it enough with it being marked with the "key" flag as this would already imply its must understand nature?
Either way it should not impact assignability but it would impact the TypeId computation.
-
Reported: DDS-XTypes 1.3b1 — Tue, 21 Mar 2023 15:27 GMT
-
Disposition: Resolved — DDS-XTypes 1.4b1
-
Disposition Summary:
Add language explaining the MemberFlag in TypeObject
Explain how MemberFlag in TypeObject is used to encode the member attributes.
-
Updated: Wed, 12 Aug 2026 16:39 GMT
DDSXTY14 — Should the TypeObject mark key members as must understand
- Key: DDSXTY14-64
- OMG Task Force: DDS Extensible Types (DDS-XTYPES) 1.4 RTF