Path: utzoo!mnetor!uunet!husc6!cmcl2!rutgers!pbox!okstate!norman
From: norman@a.cs.okstate.edu (Norman Graham)
Newsgroups: comp.lang.c++
Subject: Re: OOPS gripes (was: Generic Object Or
Message-ID: <3117@okstate.UUCP>
Date: 6 Feb 88 18:51:57 GMT
Organization: Oklahoma State Univ., Stillwater
Lines: 23

in article , keith@nih-csl.UUCP (keith gorlen) says:

> My inclination is to ignore the OOPS exception handling code as much
> as possible, and replace it when exception handling is incorporated
> into C++.

Oh joy!  You mean C++ will soon have exception handling?  I can't believe
it (Pinch, Pinch :-)!

I tried desperately to design a suitable (ie. simple, transparent, etc)
exception handling scheme for a project I'm involed with ( >80000 lines 
of C source in >450 files).  We wanted to use a stack of exception frames
and we would have, except for one problem... we couldn't guarentee that the
exception frame stack would be poped on each function return.  Of course,
it is easy for a compiler to do this.  (Guess what we ended up with...
returning a status from each function!!! Yuch!)

--
Norman Graham
Oklahoma State University              Internet:  norman@a.cs.okstate.edu
Computing and Information Sciences         UUCP:  {cbosgd, ihnp4,
219 Mathematical Sciences Building                 rutgers}!okstate!norman
Stillwater, OK  74078-0599