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

On Mon, May 01, 2006 at 09:05:30PM +0300, Yuval Kogman wrote:
> On Mon, May 01, 2006 at 19:49:41 +0100, Dave Mitchell wrote:
> > but that's roughly what a CV is anyway: it's an SV that contains pointers
> > to an op tree and a scratchpad.
> 
> 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?

-- 
Justice is when you get what you deserve.
Law is when you get what you pay for.

• [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