| Previous | Table of Contents | Next |
The data type model used in this mapping for Win32 COM is derived from MIDL (a derivative of DCE IDL). COM interfaces using
“custom marshaling? must be hand-coded and require special treatment to interoperate with CORBA using automated tools. This
specification does not address interworking between CORBA and custom-marshaled COM interfaces.
The data type model used in this mapping for Win16 COM is derived from ODL since Microsoft RPC and the Microsoft MIDL compiler
are not available for Win16. The ODL data type model was chosen since it is the only standard, high-level representation available
to COM object developers on Win16.
Note that although the MIDL and ODL data type models are used as the reference for the data model mapping, there is no requirement that either MIDL or ODL be used toimplement a COM/CORBA interworking solution.
In many cases, there is a one-to-one mapping between COM and CORBA data types.However, in cases without exact mappings, run-time conversion errors may occur.Conversion errors will be discussed in Mapping for Exception Types under
Section 18.2.10, “Interface Mapping,? on page 18-11.