Xref: utzoo comp.lang.c++:13356 comp.object:3486
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!samsung!munnari.oz.au!manuel!csis!stuarth
From: stuarth@argo.csis.dit.csiro.au (Stuart Hungerford)
Newsgroups: comp.lang.c++,comp.object
Subject: Wanted: Your error handling strategies for C++ and OOPL's
Message-ID: <1991May10.024523.244@csis.dit.csiro.au>
Date: 10 May 91 02:45:23 GMT
Organization: CSIRO Division of Information Technology
Lines: 27

Recently I've become interested in the various approaches used in OOPL's
(particularly C++) to implement error detection/handling.  I know future
versions of C++ will come with an exception handling mechanism, but I need
an approach I can use now.

The "contract" model used in Eiffel is very attractive but it really
requires compiler support to implement it.  At the other extreme the "ignore-
it-and-maybe-it-will-go-away" approach is easy to implement but probably
unacceptable in a large system.

If you have had any experiences implementing error detection/handling
mechanisms in OOPL's (particularly C++) you're willing to share, I'd really
like to hear about them.  If there's enough interest I'll summarize and
post any responses.



Stuart

+---------------------------------------------------------------------------+
| Internet : stuarth@csis.dit.csiro.au                  |                   |
| Voice    : +61-6-2750941                              |    _--_|\         |
| Fax      : +61-6-2571052                              |   /      \        |
| Postal   : CSIRO Division of Information Technology,  |   \_.--._/        |
|            GPO Box 664, Canberra ACT 2601             |         v         |
|            AUSTRALIA                                  |                   |
+---------------------------------------------------------------------------+