IDL4CPP — CORBA or non CORBA usage results in non compatible exceptions code

The spec describes that with CORBA an invalid usage of union can result in a CORBA::BAD_PARAM exception, for bounded string/vector also a CORBA::BAD_PARAM, but when not using CORBA when IDL4CSP11-9 is resolved a different exception is thrown for an union (for vector it seems this still has to be added also). When a user now has appliation code that uses IDL defined data types with and without CORBA their exception code is different. In order to achieve portability of user code I think the spec should define a omg::bad_param alias type which maps to CORBA::BAD_PARAM or the selected std exception. That way user code can be written portable when the user has data types defined by IDL and wants to support use cases with and without CORBA

Error handling and exceptions will be treated in feature versions of the spec

By design, the current version of this specification does not specify explicit mechanisms to report errors (e.g., which exception should be thrown or whether exceptions should be thrown at all). The intention was to be able to support both environments where exceptions are valid and are allowed, as well as environments where applications may not throw or handle exceptions.

Future versions of this specification may define explicit mechanisms to report errors, and will aim to harmonize them across middleware implementations.