Issue 3165: C++: ostream insertion (cxx_revision) Source: UBS (Mr. Hans Kneubuehl, hans.kneubuehl(at)ubs.com) Nature: Uncategorized Issue Severity: Summary: Many ORBs provide ostream insertion for exceptions as an extension to C++ mapping. Typically, applications are required to use them (there is not really a usable alternative) to write code in the following style: try { // do some operations } catch (CORBA::Exception & ex) { cerr << "some operation failed: " << ex << endl; } This breaks portability as not all ORBs provide the functionality in the same way. Therefore ostream insertion should be part of the standard. Resolution: closed issue, duplicate of 266 Revised Text: Actions taken: December 23, 1999: received issue December 23, 1999: closed issue, duplicate of 266 Discussion: Date: Fri, 24 Dec 1999 07:30:24 +1000 (EST) From: Michi Henning <michi@ooc.com.au> To: Juergen Boldt <juergen@omg.org> cc: issues@emerald.omg.org, cxx_revision@emerald.omg.org Subject: Re: issue 3165 -- C++ RTF issue In-Reply-To: <4.1.19991223114858.00992cc0@emerald.omg.org> Message-ID: <Pine.HPX.4.05.9912240725430.12793-100000@bobo.ooc.com.au> Organization: Object Oriented Concepts MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-UIDL: Yp]!!J5%"!JIGe9nUI!! On Thu, 23 Dec 1999, Juergen Boldt wrote: > This is issue # 3165 > > C++: ostream insertion Juergen, that's a duplicate of 266, for which a proposal is currently up for vote. So, 3165 can be closed as a duplicate. End of Annotations:===== From: hans.kneubuehl@ubs.com X-OpenMail-Hops: 2 Date: Thu, 23 Dec 1999 12:02:02 +0100 Message-Id: Subject: C++: ostream insertion MIME-Version: 1.0 TO: cxx_revision@omg.org, issues@omg.org Content-Disposition: inline; filename="BDY.TXT" ;Creation-Date="Thu, 23 Dec 1999 12:02:02 +0100" Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII ;Creation-Date="Thu, 23 Dec 1999 12:02:02 +0100" X-UIDL: ZaWd9?%Le9^$od9dhd!! I would like to raise the following issue with the C++ Language Mapping: Many ORBs provide ostream insertion for exceptions as an extension to C++ mapping. Typically, applications are required to use them (there is not really a usable alternative) to write code in the following style: try { // do some operations } catch (CORBA::Exception & ex) { cerr << "some operation failed: " << ex << endl; } This breaks portability as not all ORBs provide the functionality in the same way. Therefore ostream insertion should be part of the standard. Regards Hans -- Hans Kneubuehl, UBS AG, P.O. Box, 8098 Zurich, Switzerland phone: +41 1 238 28 96, fax: +41 1 238 30 11 Date: Fri, 24 Dec 1999 07:30:24 +1000 (EST) From: Michi Henning To: Juergen Boldt cc: issues@emerald.omg.org, cxx_revision@emerald.omg.org Subject: Re: issue 3165 -- C++ RTF issue In-Reply-To: <4.1.19991223114858.00992cc0@emerald.omg.org> Message-ID: Organization: Object Oriented Concepts MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-UIDL: Yp]!!J5%"!JIGe9nUI!! On Thu, 23 Dec 1999, Juergen Boldt wrote: > This is issue # 3165 > > C++: ostream insertion Juergen, that's a duplicate of 266, for which a proposal is currently up for vote. So, 3165 can be closed as a duplicate. 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