Issue 9575: clarify allowable (spec compliant) ways to implement ObjectReference[]. (data-distribution-rtf) Source: MITRE (Mrs. Charlotte Wales, charwing(at)mitre.org) Nature: Clarification Severity: Significant Summary: Need to clarify and/or enumerate allowable (spec compliant) ways to implement ObjectReference[]. The method definitions have return values or parameters specified by ObjectReference[]. Given that this is part of the platform independent model, it would appear that one could approach the implementation of this in C++ in one of two ways -- as std::vector<ObjectReference *> or as an ObjectReference array. It is unclear which would be the preferred spec compliant way to do this. Alternatively, one could implement this as a language specific container, vector, list, map or whatever is the best performing container for the given situation, but would that not be in compliance with the spec at all? Resolution: Revised Text: Actions taken: April 14, 2006: received issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 14 Apr 2006 18:09:49 -0400 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Charlotte Wales Company: MITRE mailFrom: charwing@mitre.org Notification: No Specification: Data Distribution Services for Real-Time Section: 3 FormalNumber: formal/05-12-04 Version: 1.1 RevisionDate: December 2005 Page: many Nature: Clarification Severity: Significant HTTP User Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 Description Need to clarify and/or enumerate allowable (spec compliant) ways to implement ObjectReference[]. The method definitions have return values or parameters specified by ObjectReference[]. Given that this is part of the platform independent model, it would appear that one could approach the implementation of this in C++ in one of two ways -- as std::vector or as an ObjectReference array. It is unclear which would be the preferred spec compliant way to do this. Alternatively, one could implement this as a language specific container, vector, list, map or whatever is the best performing container for the given situation, but would that not be in compliance with the spec at all?