2.6. Known Issues

Note

For an updated list of critical known issues, see the Critical Issues List on the RTI Customer Portal at https://support.rti.com.

2.6.1. Reopening IDL Modules not Supported by rtiddsgen for Ada

Reopening a module in IDL is not supported when using rtiddsgen for Ada. For example, the following IDL file is not supported in Ada:

module ModuleA {
    struct Struct1 {
 long longValue;
   };
};
......
module ModuleA {
   struct Struct2 {
     short shortValue;
   };
};

[RTI Issue ID CODEGENII-231]

2.6.2. API Reference HTML Documentation for Ada May be Inaccurate Regarding Internal APIs

Due to the way the online documentation is generated in this release, some of the internal APIs that are not intended to be called by users (typically with filenames ending with Low_Level.ads or impl.ads, and those APIs that are lacking detailed descriptions) may also appear in the Ada online documentation and should be ignored. When in doubt, refer to the corresponding documentation for another language to determine which APIs are meant to be public.

The parameter names mentioned in the descriptions of some of the APIs may not exactly match the actual parameter names that appear in the Ada .ads file. However, there is usually an obvious one-to-one correspondence between the parameters as described in the descriptions compared to the APIs listed in the Ada .ads file.

[RTI Issue ID CORE-6290]

2.6.3. API Reference HTML Documentation for Ada May Use Incorrect Entity Names

Links in the Ada online documentation may display wrong entity names. For example, for DDS.DomainParticipant, the displayed name may be DomainParticipant.DDS. This only affects the links. This issue is caused by AdaCore’s tool for documentation generation. RTI is investigating it with AdaCore.

[RTI Issue ID CORE-6270]