Return to the
comp.compilers page.
Search the
comp.compilers archives again.
| Related articles |
|---|
| [8 earlier articles] |
| Re: exceptions & dataflow mcdirmid@beaver.cs.washington.edu (1998-02-10) |
| Re: exceptions & dataflow jeremy@softway.com.au (1998-02-10) |
| Re: exceptions & dataflow jason@cygnus.com (Jason Merrill) (1998-02-12) |
| Re: exceptions & dataflow fjh@hydra.cs.mu.oz.au (Fergus Henderson) (1998-02-12) |
| Re: exceptions & dataflow chase@world.std.com (David Chase) (1998-02-12) |
| Re: exceptions & dataflow amitb@sasi.com (Amit Bhatnagar) (1998-02-12) |
| Re: exceptions & dataflow dlmoore@ix.netcom.com (David L Moore) (1998-02-14) |
| Re: exceptions & dataflow sergey@solyanik.com (Sergey Solyanik) (1998-02-14) |
| Re: exceptions & dataflow leichter@smarts.com (Jerry Leichter) (1998-02-14) |
| From: | David L Moore <dlmoore@ix.netcom.com> |
| Newsgroups: | comp.compilers |
| Date: | 14 Feb 1998 14:33:20 -0500 |
| Organization: | Netcom |
| References: | 98-02-055 |
| Keywords: | C++ |
Amit Bhatnagar wrote:
> I accidently found out that within a block the destructors of the
> objects inside that block are NOT called in C++. They are only called
> when the stack for the function call winds up. Do u think this is a
> good approach?
I don't believe delaying destructors until the function exits
(normally exceptions are different) rather than when the block exits
is a conforming implementation of C++. Section 12.4, para 10 of the
draft C++ standard seems to be quite explicit that calling the
destructor at block exit is required behaviour.
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.