-
Key: DDS11-104
-
Legacy Issue Number: 8558
-
Status: closed
-
Source: ADLINK Technology Ltd ( Hans van't Hag)
-
Summary:
The current IDL PSM contains the following lines:
#define HANDLE_TYPE_NATIVE long
#define HANDLE_NIL_NATIVE 0typedef HANDLE_TYPE_NATIVE InstanceHandle_t;
const InstanceHandle_t HANDLE_NIL = HANDLE_NIL_NATIVE;The two #defines can be vendor-specific. However, the constant definition in the last line restricts the HANDLE_TYPE_NATIVE to be of integer, char, wide_char, boolean, floating_pt, string, wide_string, fixed_pt or octet type; IDL does not allow any other (e.g. structured) types to be assigned a constant value.
Resolution:
The PSM contains a number of other elements that cannot be accurately expressed in IDL (e.g. static methods). As in those other cases, a comment should be added stating that structured and other non-primitive types may be used for HANDLE_TYPE_NATIVE and HANDLE_NIL_NATIVE even though IDL can't express it
Revised Text:
Mention the above in the introduction of the PSM. -
Reported: DDS 1.0 — Fri, 11 Mar 2005 05:00 GMT
-
Disposition: Resolved — DDS 1.1
-
Disposition Summary:
No Data Available
-
Updated: Fri, 6 Mar 2015 20:58 GMT
DDS11 — (T#61) Restrictive Handle definition
- Key: DDS11-104
- OMG Task Force: Data Distribution Service RTF