Dan Sugalski wrote:
>
> Tony Olekshy wrote:
> >
> >I think we need to provide some way for developers to explicitly
> >specify predictable end-of-block cleanup (using something like an
> >always block or finally clause).
>
> Attributes or other things stuck on the end of blocks strikes me as
> a
At 03:56 PM 2/12/2001 -0700, Tony Olekshy wrote:
>Dan Sugalski wrote:
> >
> > [...] I wasn't talking about try{}/finally{} stuff. I was talking
> > about DESTROY (or its equivalent) for objects, which unfortunately
> > can't be tied to any one particular place in the code.
>
>and, from another thr
Dan Sugalski wrote:
>
> [...] I wasn't talking about try{}/finally{} stuff. I was talking
> about DESTROY (or its equivalent) for objects, which unfortunately
> can't be tied to any one particular place in the code.
and, from another thread:
> I really don't want to guarantee predictable end-of
At 01:59 PM 2/12/2001 -0700, Tony Olekshy wrote:
>Dan Sugalski wrote:
> >
> > I do wish people would get garbage collection and finalization split in
> > their minds. They are two separate things which can, and will, be dealt
> > with separately.
> >
> > For the record:
> >
> > THE GARBAGE COLLECT
Dan Sugalski wrote:
>
> I do wish people would get garbage collection and finalization split in
> their minds. They are two separate things which can, and will, be dealt
> with separately.
>
> For the record:
>
> THE GARBAGE COLLECTOR WILL HAVE NOTHING TO DO WITH FINALIZATION, AND
> NO PERL OBJ
