-
Key: DDSXTY-26
-
Legacy Issue Number: 15706
-
Status: closed
-
Source: DECA ( Rick Warren)
-
Summary:
The DynamicData class, part of the Dynamic Language Binding, has a huge API consisting of many dozens of methods. This large size makes the API harder to understand and reuse.
-
Reported: DDS-XTypes 1.0b1 — Fri, 8 Oct 2010 04:00 GMT
-
Disposition: Resolved — DDS-XTypes 1.0b2
-
Disposition Summary:
Change the design of the class to reduce the size of the API. Specifically:
Replace navigation by name, ID, or index with navigation by ID only. Provide conversion methods to obtain the ID based on either of the other two. When the object is of some type for which the concept of “member ID” is not applicable (e.g. sequences), the user can nevertheless convert from the index to a “member ID” and look up based on that. It is not necessary to specify the mapping from index to ID in such cases; all that matters is that the implementation can provide one. (Where the range of indexes and IDs overlap, the “mapping” could even be a no-op.)
Coalesce access to sequences and arrays. -
Updated: Fri, 6 Mar 2015 20:58 GMT
DDSXTY — Reduce size of DynamicData API
- Key: DDSXTY-26
- OMG Task Force: Extensible and Dynamic Topic Types for DDS FTF