Issue 658: Chapter 4.3.6, Comments on DynAny (current_member_type) (port-rtf) Source: (, ) Nature: Uncategorized Severity: Summary: Summary: current_member_type operation "may return an empty string since the TypeCode of the struct being manipulated may not contain the names of members in the struct." When can this occur? Resolution: fixed, close issue Revised Text: Actions taken: August 7, 1997: received issue June 25, 1998: closed issue Discussion: End of Annotations:===== Return-Path: Date: 07 Aug 97 16:35:32 -0700 From: "JSPIRN.US.ORACLE.COM" To: issues@omg.org, port-rtf@omg.org Subject: Comments on DynAny for Portability RFP Cc: JTREZZO@us.oracle.com, DBROWER@us.oracle.com, KCOLEMAN@us.oracle.com The following issues concern the "Dynamic Any" in the portablility RFP submission. They were prepared by Kim Coleman of Oracle; I am forwarding them on in my capacity as a member of the portability RTF. Thanks, Jeff Spirn ================================= Date: 07 Aug 97 10:13:34 From:"KCOLEMAN.US.ORACLE.COM" To:jspirn Subject:Comments on DynAny for Portability Spec Cc:dbrower,tplambec,hspintzi,dlowe MIME-Version: 1.0 Content-Transfer-Encoding:7bit Content-Type:text/plain; charset="US-ASCII" Comments on Chapter 4 (DynAny) of orbos/97-04-14 (Portability spec) 4.3.6 ----- The current_member_name operation "may return an empty string since the TypeCode of the struct being manipulated may not contain the names of members in the struct". When can this occur? You cannot construct a well-formed struct typecode that doesn't include the member names, can you? If this is meant to refer to the fact that exceptions may not have any members, then the current_member_kind needs to allow for this possibility as well. > 4.3.6 > ----- > The current_member_name operation "may return an empty string since > the TypeCode of the struct being manipulated may not contain the > names of > members in the struct". When can this occur? You cannot construct a > well-formed struct typecode that doesn't include the member names, > can you? > Return-Path: Sender: jon@sems.com Date: Fri, 08 Aug 1997 09:39:56 -0700 From: Jonathan Biggar Organization: Seagate Software, Network & Storage Management Group To: "JSPIRN.US.ORACLE.COM" Cc: issues@omg.org, port-rtf@omg.org, JTREZZO@us.oracle.com, DBROWER@us.oracle.com, KCOLEMAN@us.oracle.com Subject: Re: Comments on DynAny for Portability RFP References: <199708080659.XAA15448@mailsun2.us.oracle.com> My comments are integrated below: If you read the TypeCode information in the CORBA 2.0 spec, section 6.7.1, youwill find that the member_name operation may return an empty string. My understanding is that typecodes that are fetched from the Interface Repository are the only typecodes that are required to have the id(), name() and member_name() strings all defined correctly. Any other typecode, generated by the IDL compiler or by the ORB create_*_tc() operations are allowed to have empty strings in order to save space and time on the wire. > If this is meant to refer to the fact that exceptions may not have any > members, then the current_member_kind needs to allow for this possibility > as well.