Issue 15834: DDS specification should be more precise on NATIVE defines (data-distribution-rtf) Source: Remedy IT (Mr. Johnny Willemsen, jwillemsen(at)remedy.nl) Nature: Clarification Severity: Significant Summary: DDS leaves domainid, handle, and topic key to the dds vendor, each can define their own type for these. The specification has defines for them, but the default is long. If now a vendor uses for example a struct for the InstanceHandle_t, this leads to challenges when writing portable C++ code because the argument passing is different between a long (as value) or a fixed struct (const &). To my idea the dds specification should be more precise on the type, maybe fixed struct to achieve more portability of users code Resolution: Revised Text: Actions taken: November 17, 2010: received issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 17 Nov 2010 13:24:30 -0500 To: Subject: Issue/Bug Report ******************************************************************************* Name: Johnny Willemsen Employer: Remedy IT mailFrom: jwillemsen@remedy.nl Terms_Agreement: I agree Specification: DDS Section: 7.2.3 FormalNumber: 07-01-01 Version: 1.2 Doc_Year: 2007 Doc_Month: January Doc_Day: 01 Page: 145 Title: DDS specification should be more precise on NATIVE defines Nature: Clarification Severity: Significant CODE: 3TMw8 B1: Report Issue Description: DDS leaves domainid, handle, and topic key to the dds vendor, each can define their own type for these. The specification has defines for them, but the default is long. If now a vendor uses for example a struct for the InstanceHandle_t, this leads to challenges when writing portable C++ code because the argument passing is different between a long (as value) or a fixed struct (const &). To my idea the dds specification should be more precise on the type, maybe fixed struct to achieve more portability of users code