Issue 3762: Anonymous types in OTS (ots-rtf) Source: Triodia Technologies Pty Ltd (Mr. Michi Henning, michi(at)triodia.com) Nature: Uncategorized Issue Severity: Summary: CORBA 2.4 deprecates anonymous types, but there are two in the OTS spec: struct otid_t { long format_id; /* format identifier. 0 is OSI TP */ long bqual_length; sequence <Octet> tid; }; struct PropagationContext { unsigned long timeout; TransIdentity current; sequence <TransIdentity> parents; any implementation_specific_data; }; I think we should use: struct otid_t { long format_id; /* format identifier. 0 is OSI TP */ long bqual_length; CORBA::OctetSeq tid; }; typedef sequence<TransIdentity> TransIdentitySeq; struct PropagationContext { unsigned long timeout; TransIdentity current; TransIdentitySeq parents; any implementation_specific_data; }; Resolution: Revised Text: Actions taken: July 25, 2000: received issue Discussion: End of Annotations:===== Date: Tue, 25 Jul 2000 08:43:41 +1000 (EST) From: Michi Henning Reply-To: OTS RTF To: OTS RTF cc: issues@omg.org Subject: Anonymous types in OTS Message-ID: Organization: Object Oriented Concepts MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-UIDL: h;od9fgEe9m"Y!!U5(e9 Hi, CORBA 2.4 deprecates anonymous types, but there are two in the OTS spec: struct otid_t { long format_id; /* format identifier. 0 is OSI TP */ long bqual_length; sequence tid; }; struct PropagationContext { unsigned long timeout; TransIdentity current; sequence parents; any implementation_specific_data; }; I think we should use: struct otid_t { long format_id; /* format identifier. 0 is OSI TP */ long bqual_length; CORBA::OctetSeq tid; }; typedef sequence TransIdentitySeq; struct PropagationContext { unsigned long timeout; TransIdentity current; TransIdentitySeq parents; any implementation_specific_data; }; Cheers, Michi. -- Michi Henning +61 7 3891 5744 Object Oriented Concepts +61 4 1118 2700 (mobile) Suite 4, 904 Stanley St +61 7 3891 5009 (fax) East Brisbane 4169 michi@ooc.com.au AUSTRALIA http://www.ooc.com.au/staff/michi-henning.html X-Sender: ecobb@svlhome2.beasys.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Mon, 24 Jul 2000 15:49:27 -0700 To: michiOTS RTF From: Edward Cobb Subject: Re: Anonymous types in OTS Cc: OTS RTF In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-UIDL: _J`d9I!D!!X*F!![ood9 Sounds right to me... At 08:43 AM 7/25/00 +1000, Michi Henning wrote: >Hi, > >CORBA 2.4 deprecates anonymous types, but there are two in the OTS spec: > >struct otid_t >{ > long format_id; /* format identifier. 0 is OSI TP */ > long bqual_length; > sequence tid; >}; > >struct PropagationContext >{ > unsigned long timeout; > TransIdentity current; > sequence parents; > any implementation_specific_data; >}; > >I think we should use: > >struct otid_t >{ > long format_id; /* format identifier. 0 is OSI TP */ > long bqual_length; > CORBA::OctetSeq tid; >}; > >typedef sequence TransIdentitySeq; > >struct PropagationContext >{ > unsigned long timeout; > TransIdentity current; > TransIdentitySeq parents; > any implementation_specific_data; >}; > > Cheers, > > Michi. >-- >Michi Henning +61 7 3891 5744 >Object Oriented Concepts +61 4 1118 2700 (mobile) >Suite 4, 904 Stanley St +61 7 3891 5009 (fax) >East Brisbane 4169 michi@ooc.com.au >AUSTRALIA http://www.ooc.com.au/staff/michi-henning.html > > > ************************************************************** Ed Cobb, Vice President, Advanced Technology & Standards BEA Systems, Inc., 2315 North First St., San Jose, CA 95131 Tel: 408-570-8264 / Fax: 408-570-8942 E-mail: ed.cobb@beasys.com ************************************************************** From: "Mark Little" To: "OTS RTF" References: Subject: Re: Anonymous types in OTS Date: Tue, 25 Jul 2000 09:00:12 +0100 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Content-Type: text/plain; charset="iso-8859-1" X-UIDL: k5Vd95lJ!!`Did9`7_d9 > I think we should use: > > struct otid_t > { > long format_id; /* format identifier. 0 is OSI TP >*/ > long bqual_length; > CORBA::OctetSeq tid; > }; > > typedef sequence TransIdentitySeq; > > struct PropagationContext > { > unsigned long timeout; > TransIdentity current; > TransIdentitySeq parents; > any implementation_specific_data; > }; Agreed. Quite a few idl compilers didn't support them anyway, which I think was very forward thinking on behalf of their implementers ;-) Mark. ----------------------------------------------------------------------- SENDER : Dr. Mark Little, Architect (Transactions), Arjuna Solutions PHONE : +44 191 222 8066, FAX : +44 191 222 8232 EMAIL : mark@arjuna.com Sender: jis@fpk.hp.com Message-ID: <397DAC1A.E6C70131@fpk.hp.com> Date: Tue, 25 Jul 2000 11:02:50 -0400 From: Jishnu Mukerji Organization: Hewlett-Packard EIAL X-Mailer: Mozilla 4.08 [en] (X11; U; HP-UX B.10.10 9000/777) MIME-Version: 1.0 To: Edward Cobb Cc: Michi Henning , OTS RTF Subject: Re: Anonymous types in OTS References: <3.0.5.32.20000724155001.00b8d9e0@svlhome2.beasys.com> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii X-UIDL: 2Ci!!AWK!!2?/e9h75e9 Edward Cobb wrote: > > Sounds right to me... > > At 08:43 AM 7/25/00 +1000, Michi Henning wrote: > >Hi, > > > >CORBA 2.4 deprecates anonymous types, but there are two in the OTS spec: > > > >struct otid_t > >{ > > long format_id; /* format identifier. 0 is OSI TP */ > > long bqual_length; > > sequence tid; > >}; > > > >struct PropagationContext > >{ > > unsigned long timeout; > > TransIdentity current; > > sequence parents; > > any implementation_specific_data; > >}; > > > >I think we should use: > > > >struct otid_t > >{ > > long format_id; /* format identifier. 0 is OSI TP */ > > long bqual_length; > > CORBA::OctetSeq tid; > >}; > > > >typedef sequence TransIdentitySeq; > > > >struct PropagationContext > >{ > > unsigned long timeout; > > TransIdentity current; > > TransIdentitySeq parents; > > any implementation_specific_data; > >}; So how do we exactly propose to incorporate this change in a backward compatible manner? Can't just replace this with that inside a struct with the same name, can we? Jishnu. -- Jishnu Mukerji Systems Architect Email: jis@fpk.hp.com Hewlett-Packard EIAL, Tel: +1 973 443 7528 300 Campus Drive, 2E-62, Fax: +1 973 443 7422 Florham Park, NJ 07932, USA. Date: Wed, 26 Jul 2000 06:35:51 +1000 (EST) From: Michi Henning To: Jishnu Mukerji cc: Edward Cobb , OTS RTF Subject: Re: Anonymous types in OTS In-Reply-To: <397DAC1A.E6C70131@fpk.hp.com> Message-ID: Organization: Object Oriented Concepts MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-UIDL: )R7!!hQ%e9?,Pd9[7S!! On Tue, 25 Jul 2000, Jishnu Mukerji wrote: > So how do we exactly propose to incorporate this change in a backward compatible manner? Can't just > replace this with that inside a struct with the same name, can we? Well, the type hasn't actually changed, so the marshaling and everything else is still exactly the same. It would affect clients that use the IFR and somehow expect that particular member to be anonymous instead of a typedef. However, I don't expect that there will be such clients. If there are clients that actually do use the DII for that particular structure, they would be able to handle the typedef too. So, I think we can actually get away with this... Cheers, Michi. -- Michi Henning +61 7 3891 5744 Object Oriented Concepts +61 4 1118 2700 (mobile) Suite 4, 904 Stanley St +61 7 3891 5009 (fax) East Brisbane 4169 michi@ooc.com.au AUSTRALIA http://www.ooc.com.au/staff/michi-henning.html