Add support for IDL4

[jwillemsen]

Add support for IDL4

[jwillemsen]

https://github.com/jwillemsen/ridl/tree/jwi-idl4basictypes contains a proof of concept for extending the basic types. The IDL version has to be passed to the parser, the keywords extension should be conditional based on the IDL version, see https://github.com/jwillemsen/ridl/tree/jwi-idlversion4

See https://github.com/jwillemsen/taox11/tree/jwi-idl4basictypes for the test extension

RIDL should set a define for the IDL version that is set, for example 3.5 or 4.0/4.1/4.2, etc

[jwillemsen]

https://github.com/jwillemsen/taox11/tree/jwi-idl4typessupport has some proof of concept for map. see https://github.com/jwillemsen/ridl/tree/jwi-idl4typessupport for the related RIDL grammar extensions

[jwillemsen]

Adding support for IDL4 is a large effort, first step is to add IDL4 support to RIDL, after that it requires extensions to TAOX11 and all backends. For all types it has be analyzed and implemented how these new types can be transferred through the wire. TAO/TAO_IDL/OpenDDS/CORBA don't support all types yet, so also there research and development has to be done

[jwillemsen]

When we allow IDL4 types to be used for AXCIOMA it also implies user can use these new types as component attributes, which implies we need to support these new types in the XML/config file parsing, which also requires DynamicAny/Typecode support for these types, another large additional effort. When that has been added also the modeling tools need support for these new IDL4 types (including their IDL/CDP generators)

[jwillemsen]

WiP map support for TAO: DOCGroup/ACE_TAO#1842
WiP map support for OpenDDS: OpenDDS/OpenDDS#3603

[jwillemsen]

Adding the IDL4 types to the wire protocols will cause interoperability issues, for CORBA very likely a new GIOP revision has to be defined

[jwillemsen]

Experimental support for idl4 grammar is available on master