Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!ncar!gatech!mcnc!decvax!decwrl!pyramid!hplabs!hp-pcd!hplsla!jima
From: jima@hplsla.HP.COM (              Jim Adcock)
Newsgroups: comp.lang.c++
Subject: Re: Proposal for Exceptions for C++
Message-ID: <6590029@hplsla.HP.COM>
Date: 8 Apr 88 03:32:46 GMT
References: <8180006@eecs.nwu.edu>
Organization: HP Lake Stevens, WA
Lines: 14

| That's the easy part.  How does your implementation arrange to execute
| the destructors of class objects that go out of scope as a result of
| an exception?

Well now, there seems to be several people who claim to have solutions
to the C++ exception problem, but I have yet to see anyone explain how
to call destructors for the objects going out of scope.

If someone HAS figured out a good solution to this problem, how about a 
quick explanation?

[under the restriction that any object on the stack (that needs to be
 destroyed when an exception trashes its environment) has a vtable,
 this problem becomes quite doable.  Anybody have found a less 
 restrictive (and reasonable) solution? ]