stuarth@argo.csis.dit.csiro.au (Stuart Hungerford) (05/10/91)
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 | | +---------------------------------------------------------------------------+
miller@intvax.UUCP (Dave Miller) (05/11/91)
I also need all the information and available code I can get on error handling strategies, so please mail or post summary. Thanks, Dave Miller Sandia National Labs miller@intvax!unmvax.cs.unm.edu
grooke@tcom.stc.co.uk (Gill Rooke) (05/13/91)
There are a lot of us with this interest, so please publish a summary. Ts Gil.