Related articles |
---|
[9 earlier articles] |
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: | "Sergey Solyanik" <sergey@solyanik.com> |
Newsgroups: | comp.compilers |
Date: | 14 Feb 1998 14:39:47 -0500 |
Organization: | Bentley Systems, Inc |
References: | 98-02-055 |
Keywords: | dataflow, Java |
Amit Bhatnagar <amitb@sasi.com> wrote
> I would prefer that all the destructors for the local block be called
> as soon as the scope of the variable is over.
>
> I am not familiar with Java, but is a 'finalizer' similar kind of a
> concept?
Actually, finalizer in Java is called when object is garbage
collected. That is, you can not predict when and in what sequence
finalizers will be called, and in non-accurate garbage colectors, if
they will ever be called.
Regards --
Sergey Solyanik
Software Developer
Bentley Systems, Inc
Sergey.Solyanik@bentley.com
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.