Issue 2009:  COM/CORBA keywords (issues)
Source:  (, )
Nature:  Uncategorized Issue
Severity: 
Summary: Summary: I can"t find in the COM/CORBA spec parts A and B any mention of how to
 deal with IDL identifiers that are keywords to the Microsoft "mktyplib" tool.
 This tool mangles the following identifier (not necessarily a complete list) by
 prepending them with "_":
 
         "BSTR", "CALLCONV", "coclass", "CY",
         "CURRENCY", "DATE", "DECIMAL", "DISPID", "DISPPARAMS",
         "dual", "EXCEPINFO", "guid", "GUID",
         "HRESULT", "importlib", "IDispatch",
         "INTERFACEDATA", "IUnknown", "LCID",
         "METHODDATA", "odl", "oleautomation",
         "PARAMDATA", "properties", "propget", "propput", "retval",
         "SAFEARRAY", "SAFEARRAYBOUND", "SCODE",
         "VARIANT", "VARIANTARG", "VARIANT_BOOL",
         "VARTYPE", "VARENUM"
 
 As far as I can tell, the output of the "mktyplib" tool makes use 
 (directly or indirectly) of the regular C++ bindings, whose identifiers
 are not mangled the same way.  This makes it impossible to emit COM bindings
 for IDL files that contain the above keywords.
 
 The problem that I"m running into is in CosTrading IDL, where the identifier
 "properties" is used.
 

Resolution: 
Revised Text: 
Actions taken:
September 29, 1998: received issue
Discussion: 

End of Annotations:=====
Return-Path: <mcheng@austin.ibm.com>
Date: Tue, 29 Sep 1998 09:25:17 -0500
From: mcheng@austin.ibm.com (Michael Cheng)
To: issues@omg.org
Subject: COM/CORBA keywords (resend)
Cc: dnimtz@us.ibm.com, mcheng@us.ibm.com

I can't find in the COM/CORBA spec parts A and B any mention of how to
deal with IDL identifiers that are keywords to the Microsoft
"mktyplib" tool.
This tool mangles the following identifier (not necessarily a complete
list) by
prepending them with "_":

        "BSTR", "CALLCONV", "coclass", "CY",
        "CURRENCY", "DATE", "DECIMAL", "DISPID", "DISPPARAMS",
        "dual", "EXCEPINFO", "guid", "GUID",
        "HRESULT", "importlib", "IDispatch",
        "INTERFACEDATA", "IUnknown", "LCID",
        "METHODDATA", "odl", "oleautomation",
        "PARAMDATA", "properties", "propget", "propput", "retval",
        "SAFEARRAY", "SAFEARRAYBOUND", "SCODE",
        "VARIANT", "VARIANTARG", "VARIANT_BOOL",
        "VARTYPE", "VARENUM"

As far as I can tell, the output of the "mktyplib" tool makes use 
(directly or indirectly) of the regular C++ bindings, whose
identifiers
are not mangled the same way.  This makes it impossible to emit COM
bindings
for IDL files that contain the above keywords.

The problem that I'm running into is in CosTrading IDL, where the
identifier
"properties" is used.

---------------------------------------------------------------------------
Michael Cheng                                          Ph :
512-823-7442
IBM Component Broker                                   Fax:
512-838-1032
mcheng@us.ibm.com                                      TIE:
793-7442