Issue 2458: Name and scope of instantiation of CORBA.Sequences.{Un}Bounded (ada-rtf) Source: (, ) Nature: Revision Severity: Summary: Summary: CORBA V2.2 section 23.5.6, Mapping for Sequence Types, states that " The name and scope of the instantiation [of CORBA.Sequences.Bounded or CORBA.Sequences.Unbounded] is left implementation defined. " However, the drawing.idl mapping example in the same section suggests that 1) the name of the instantiation be the simple_type_spec with "IDL_SEQUENCE_" prepended 2) the instantiation be located within the same scope as the corresponding IDL sequence type declaration. (This could be expanded to state that if the sequence type declaration appears at the IDL file scope level, then the instantation shall appear within the synthesized IDL_FILE_ package.) Resolution: Revised Text: Actions taken: February 19, 1999: received issue June 4, 1999: closed issue Discussion: End of Annotations:===== BBBBBBBBBBBBBBBBBBFrom: "Oliver M. Kellogg" To: Subject: Name and scope of instantiation of CORBA.Sequences.{Un}Bounded Date: Fri, 19 Feb 1999 11:45:04 +0100 X-Msmail-Priority: Normal Issue type: revision CORBA V2.2 section 23.5.6, Mapping for Sequence Types, states that " The name and scope of the instantiation [of CORBA.Sequences.Bounded or CORBA.Sequences.Unbounded] is left implementation defined. " However, the drawing.idl mapping example in the same section suggests that 1) the name of the instantiation be the simple_type_spec with "IDL_SEQUENCE_" prepended 2) the instantiation be located within the same scope as the corresponding IDL sequence type declaration. (This could be expanded to state that if the sequence type declaration appears at the IDL file scope level, then the instantation shall appear within the synthesized IDL_FILE_ package.) Various Ada mapping implementations handle the name and scope issue in different ways, which creates non- portability. I propose to formalize the name and scope rules. Thanks, Oliver M. Kellogg DaimlerChrysler Aerospace Sensor Systems, Dept. VE3SW5 D-89070 Ulm, Germany phone: (+49) 731 392-7138 fax: (+49) 731 392-4255 e-mail: Oliver.Kellogg@vs.dasa.de From: "Oliver Kellogg" To: Subject: ptc/99-02-02: resolution of issue 2458 Date: Mon, 17 May 1999 16:38:11 +0200 X-Msmail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1161 Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by emerald.omg.org id KAA04924 Content-Type: text/plain; charset=ISO-8859-1 X-UIDL: 96c83980ad799bd741edaea8194ba89a The resolution of issue 2458, Name and scope of instantiation of CORBA.Sequences.{Un}Bounded, reads: > It is not a portability issue since the user only uses the > type and derived operations declared in the IDL-mapped scope. That is not true in the case of on-the-fly sequence type declarations: // IDL struct stru { sequence octseq; }; To operate on the octseq member, the user must directly use the generated IDL_Sequence_octet package. Thanks, Oliver M. Kellogg DaimlerChrysler Aerospace e-mail: oliver.kellogg@vs.dasa.de From: "Oliver Kellogg" To: Subject: ptc/99-02-02: resolution of issue 2458 Date: Mon, 17 May 1999 16:38:11 +0200 X-Msmail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1161 Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by emerald.omg.org id KAA04924 Content-Type: text/plain; charset=ISO-8859-1 X-UIDL: 96c83980ad799bd741edaea8194ba89a The resolution of issue 2458, Name and scope of instantiation of CORBA.Sequences.{Un}Bounded, reads: > It is not a portability issue since the user only uses the > type and derived operations declared in the IDL-mapped scope. That is not true in the case of on-the-fly sequence type declarations: // IDL struct stru { sequence octseq; }; To operate on the octseq member, the user must directly use the generated IDL_Sequence_octet package. Thanks, Oliver M. Kellogg DaimlerChrysler Aerospace e-mail: oliver.kellogg@vs.dasa.de