Issue 1519: _var & _out types problems (01) (cxx_revision) Source: (, ) Nature: Revision Severity: Summary: Summary: 1. The spec insection 20.9.2 does not specifically address the form of T_out types for fixed length structured types. So, should the T_out type be: typedef T &T_out; or should it follow the form of the T_out type for variable length structured types and define as a "class T_out"? In this case, of course the copy contructor operator from T_var would not delete the pointer held by the T_var. Since the "class T_out" solution for fixed length types does not appear to have any advantages over the typedef, I recommend that the spec be modified to state that T_out types for fixed length structured types simply be a typedef of "T&". Resolution: see below Revised Text: Preceding the final paragraph of 1.9.2, add the following para: For fixed-length underlying types, no memory management issues arise; however, a compliant mapping must provide the following type definition in the scope of T: typedef T &T_out; Actions taken: June 10, 1998: received issue May 13, 2002: closed issue Discussion: End of Annotations:===== Return-Path: Sender: jon@floorboard.com Date: Wed, 10 Jun 1998 12:15:04 -0700 From: Jonathan Biggar To: issues@omg.org, cxx_revision@omg.org Subject: Problems related to _var & _out types in C++ language mapping 1. The spec insection 20.9.2 does not specifically address the form of T_out types for fixed length structured types. So, should the T_out type be: typedef T &T_out; or should it follow the form of the T_out type for variable length structured types and define as a "class T_out"? In this case, of course the copy contructor operator from T_var would not delete the pointer held by the T_var. Since the "class T_out" solution for fixed length types does not appear to have any advantages over the typedef, I recommend that the spec be modified to state that T_out types for fixed length structured types simply be a typedef of 'T&'. Date: Mon, 28 May 2001 13:14:53 +1000 (EST) From: Michi Henning Reply-To: C++ Revision Task Force To: C++ Revision Task Force Subject: Proposal for 1519 Message-ID: Organization: IONA Technologies MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-UIDL: 5R[d9))nd9eUS!!68R!! Status: RO Proposal for 1519: Preceding the final paragraph of 1.9.2, add the following para: For fixed-length underlying types, no memory management issues arise; however, a compliant mapping must provide the following type definition in the scope of T: typedef T &T_out; Cheers, Michi. -- Michi Henning +61 7 3324 9633 Chief CORBA Scientist +61 4 1118 2700 (mobile) IONA Technologies +61 7 3324 9799 (fax) Total Business Integration http://www.ooc.com.au/staff/michi