Legacy Issue Number: 13839
Source: Airbus Group ( Oliver Kellogg)
The mapping of user written IDL to C++ is not described in the version 1.2 of the DDS standard.
Is it expected that DDS use the existing CORBA C++ mapping for data types? If so then the standard should state this requirement.
On the other hand, the CORBA IDL to C++ mapping is fairly old. The new DDS PSM for C++ would suggest a more modern mapping.
For example, for bounded strings and bounded sequences, C++ classes inspired by the Standard Template Library (STL) could be used. These classes need not necessarily break the DCPS compatibility with the C language mentioned in 126.96.36.199. (Use fixed buffer, avoid virtual methods.) It is not clear whether unbounded data types need be supported, see issues 8892 and 12360.
In case a new mapping is defined which is independent of the CORBA C++ mapping, there is a problem to address:
Bridge applications which use both CORBA and DDS would need to translate a single IDL file twice, once for CORBA and again for DDS. Then there is an overlap in the generated names. This problem could be solved by encapsulating all C++ code generated for DDS from user IDL in an extra namespace.
Reported: DDS 1.2 — Fri, 27 Mar 2009 04:00 GMT
Updated: Thu, 10 Oct 2019 00:03 GMT