-
Notifications
You must be signed in to change notification settings - Fork 386
Anonymous Types in IDL4 #1135
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Anonymous Types in IDL4 #1135
Conversation
This just uses the existing IDL2 support to enable using them in IDL4, but it's not know how good that support is. At the very least a new test will have to be made in tests/IDLv4.
Not all language mappings do support anonymous types, the IDL to C++11 language mapping doesn't support them because it is impossible to use IDL::traits for template meta programming when anonymous types are used in user IDL. Personally I was not in favor of adding them back to IDL4, there was a reason to deprecate them in the past. |
Language mappings based on IDL3 should use the IDL3 settings of tao_idl.
We can't do anything about that at this point, since they are widely used in XTypes and other DDS specs, and also in ROS2. |
:-( regret to hear that, it is a small effort to just add a typedef and use that. It would make template meta programming using IDL::traits so much easier for the user, especially in the DDS world where a lot of APIs are just templated APIs. |
+1
Similar in Ada where they create problems due to the language's particularly strong typing. |
We should make it possible for the user to enable IDL4 but disallow anonymous types so that any developments using TAO doesn't break Ada/C++11 parts of the same system later on |
To allow incompatible backends to avoid having to deal with anonymous types when using IDL4.
Alright now it should be possible to override the IDL4 anonymous behavior from the backend or the command line the same as with IDL3. |
When you tested this I am ok |
No description provided.