-
Key: CORBA24-45
-
Legacy Issue Number: 3048
-
Status: closed
-
Source: ZeroC ( Marc Laukien)
-
Summary:
At present, the following IDL code is illegal:
interface I
{ CORBA::TypeCode get_type(); };
To make it legal, "orb.idl" must be included. From the spec:
"The file orb.idl contains the IDL definitions for the CORBA module. The
file orb.idl must be included in IDL files that use names defined in the
CORBA module."I don't think that this is a good idea, because of the following
reasons:- TypeCode is PIDL, not IDL. So orb.idl can only be used as a "switch"
to enable TypeCode, but it cannot contain a "real" IDL definition for
TypeCode.
- Having to include orb.idl for every little program that requires
TypeCode means a huge overhead, as orb.idl includes everything from
the CORBA module (including the IFR!).
I don't see any reason why TypeCode should only be available if orb.idl
is included. To me, TypeCode is "built-in", even if it doesn't have a
keyword. So it appears rather strange to me that I have to artificially
disable TypeCode in our IDL parser if orb.idl is not included, just to
be compliant with the spec.I would therefore propose to allow CORBA::TypeCode in IDL even if
orb.idl is not included. - TypeCode is PIDL, not IDL. So orb.idl can only be used as a "switch"
-
Reported: CORBA 2.3.1 — Tue, 23 Nov 1999 05:00 GMT
-
Disposition: Resolved — CORBA 2.4
-
Disposition Summary:
No Data Available
-
Updated: Fri, 6 Mar 2015 20:58 GMT