Xref: utzoo gnu.g++.help:520 comp.lang.c++:11899
Path: utzoo!utgpu!watserv1!watmath!uunet!tut.cis.ohio-state.edu!unreplyable!garbage
From: simmel@oberon.com (Sergiu Simmel)
Newsgroups: gnu.g++.help,comp.lang.c++
Subject: Exceptions & g++
Message-ID: <9102252331.AA02051@iago.oberon.com>
Date: 25 Feb 91 23:31:49 GMT
Sender: daemon@tut.cis.ohio-state.edu
Followup-To: gnu.g++.help
Organization: Gatewayed from the GNU Project mailing list help-g++@prep.ai.mit.edu
Lines: 32

I am trying to establish a policy for using exceptions in C++ programming
for my company. A few questions:

- is there a serious intent to migrate (or switch) g++'s exception mechanism
  to the one of the proposed ANSI C++ (per Ellis/Strostrup book)?

- if so, when to expect that? If the answer is 'in g++ 2.x', then when
  can one expect that release?

- if answers to the above unknown or not public, then what do you recommend
  we do if (a) we'd like to be very standard in our use of C++, (b)
  we must use exceptions (error codes won't do), (c) we'd like to have
  little or no code to adjust or redo for this reason in the future.

  Is there a non-empty solution satisfying the above three constraints?

- has anybody that you know of faced and resolved the same problem or similar?
  If so, can you provide pointers, sketch their solutions, etc.?

Please help. We _must_ make a decision very soon, and I can use all the help
I can get.

Please respond via e-mail (and _not_ by posting to the newsgroup, because
for a while I won't be able to monitor the news reliably) to:

             simmel@oberon.com

Thank you for your help.

---Sergiu Simmel---
Oberon Software, Inc.
Cambridge, Massachusetts