10.4.10. Generated Code (C, Traditional C++, and Modern C++)

10.4.10.1. [Major] Type registration API did not consistently report errors

The DomainParticipant register_type API should fail if a data type’s maximum serialized size exceeds 4GB. However, code that was generated with interpreted 0 would not cause the API to fail. Now, type registration fails consistently for types larger than 4 GB.

[RTI Issue ID MICRO-9889]

10.4.10.2. [Minor] Build error when generating an IDL that contained a long double on unsupported systems

When generating an IDL that contained a long double on systems that don’t natively support long double, the resulting code would have an invalid variable.

[RTI Issue ID MICRO-3031]

10.4.10.3. [Minor] Superflous parent member generated in a derived C++ class when using -interpreted 0

When generating code using the rtiddsgen option -interpreted 0 , a superflous parent member was generated in a derived C++ class.

[RTI Issue ID MICRO-2714]

10.4.10.4. [Minor] Generated AUTOSAR files placed in the wrong folder for AUTOSAR_CDD

This issue was introduced in release 4.3.0 ER1 and did not impact release 4.2.0.

When running rtiddsmag for the AUTOSAR_CDD application type, Appgen.c, Appgen.h, and DdsCddType.arxml were placed in the wrong folder if the application name was anything other than MCU_DDS_CDD.

[RTI Issue ID MAG-408]

10.4.10.5. [Trivial] Code Generator did not find Java when run from default directory

The rtiddsgen script could not locate the installed Java Runtime Environment (JRE) when run directly from the bin/ directory.

[RTI Issue ID MICRO-11600]