![]() |
![]() |
![]() |
![]() |
![]() |
For a description of OMG IDL grammar, see Chapter 3 of the Common Object Request Broker: Architecture and Specification Revision 2.4 “OMG IDL Syntax and Semantics.”
•
Note: Because CORBA 2.4 states that the native type declaration is intended for use in Object Adapters, not user interfaces, this type is available in the PortableServer module only for clients that support callbacks, that is, joint client/servers.
•
Note: Support for the long long, unsigned long long, wchar, and wstring data types was added to Oracle Tuxedo CORBA in release 8.0.The IDL compiler defines preprocessor macros specific to the platform. All macros predefined by the preprocessor that you are using can be used in the OMG IDL file, in addition to the user-defined macros. You can also define your own macros when you are compiling or loading OMG IDL files.Table 1‑1 describes the predefined macros for each platform.
Table 1‑1 Predefined Macros Table 1‑2 describes constraints for the Oracle Tuxedo 9.1 C++ IDL compiler and provides information about recommended workarounds.
Table 1‑2 C++ IDL Compiler
•
•
• C++ compilers report an error that an "operator <<" is ambiguous and that there is no "operator>>" for type char. These errors are produced because of the multiple levels of typedefs; the C++ compiler may not associate the type X::b with CORBA::Boolean because of the intermediate type definition of X::a. Use a single level of indirection when you define char or boolean types. In the IDL example above, the attribute ‘X::Z’ would be defined using either the standard type ‘boolean’ or the user type ‘X::a’, but not the user type ‘X::b’.