Path: utzoo!mnetor!uunet!husc6!mailrus!nrl-cmf!cmcl2!brl-adm!umd5!cvl!elsie!nih-csl!keith
From: keith@nih-csl.UUCP (keith gorlen)
Newsgroups: comp.lang.c++
Subject: Re: Proposal for Exceptions for C++
Message-ID: <320@nih-csl.UUCP>
Date: 9 Apr 88 15:26:22 GMT
References: <8180006@eecs.nwu.edu> <6590029@hplsla.HP.COM>
Organization: NIH-CSL, Bethesda, MD
Lines: 17
Summary: How does having a vtable help getting destructors called
	 when an exception occurs?

In article <6590029@hplsla.HP.COM>, jima@hplsla.HP.COM (              Jim Adcock) writes:
-> 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.
-> ...
-> [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? ]

How does heving a vtable help?

-- 
	Keith Gorlen			phone: (301) 496-5363
	Building 12A, Room 2017		uucp: uunet!ncifcrf.gov!nih-csl!keith
	National Institutes of Health	Internet: keith%nih-csl@ncifcrf.gov
	Bethesda, MD 20892