Re: [perl #3306] DESTROY doesn't get called.

On Mon, May 01, 2006 at 20:55:21 +0100, Dave Mitchell wrote:
> > Oh... I was assuming if it were that way then the optimization would
> > not be so substantial ;-)
> 
> I should imagine it's copying the scratchpad that takes most of the time.
> Hmm, perhaps we could just share the scratchpads for non-closure anon
> subs?

Why is it copied? I guessed (in my prior email) that it's not
captured vars, but just the sub proto and allocation info, right?
In general the only runtime writable part of the scratch pad are the
free variables... Perhaps closures should have the pad split up?

-- 
  Yuval Kogman <nothingmuch@woobling.org>
http://nothingmuch.woobling.org  0xEBD27418

• [perl #3306] DESTROY doesn't get called. by Steve Peters via RT
• Re: [perl #3306] DESTROY doesn't get called. by Dave Mitchell
• Re: [perl #3306] DESTROY doesn't get called. by Yuval Kogman
• Re: [perl #3306] DESTROY doesn't get called. by Dave Mitchell
• Re: [perl #3306] DESTROY doesn't get called. by Yuval Kogman
• Re: [perl #3306] DESTROY doesn't get called. by Dave Mitchell
• Re: [perl #3306] DESTROY doesn't get called. by Nicholas Clark
• Re: [perl #3306] DESTROY doesn't get called. by Yuval Kogman
• Re: [perl #3306] DESTROY doesn't get called. by Dave Mitchell
• Re: [perl #3306] DESTROY doesn't get called. by Dave Mitchell
• [perl #3306] DESTROY not called on code reference objects by Father Chrysostomos via RT
• Re: [perl #3306] DESTROY not called on code reference objects by Dave Mitchell
• Re: [perl #3306] DESTROY not called on code reference objects by John Siracusa
• Re: [perl #3306] DESTROY doesn't get called. by Yuval Kogman
• Re: [perl #3306] DESTROY doesn't get called. by Dave Mitchell