develooper Front page | perl.perl5.porters | Postings from February 2003

Re: [PATCH] jumbo closure fix

Thread Previous | Thread Next
From:
Dave Mitchell
Date:
February 27, 2003 05:23
Subject:
Re: [PATCH] jumbo closure fix
Message ID:
20030227132009.E17277@fdgroup.com
On Thu, Feb 27, 2003 at 01:45:37PM +0100, A Bergman wrote:
> 
> On torsdag, feb 27, 2003, at 13:19 Europe/Stockholm, Dave Mitchell 
> wrote:
> > It's just another global used during the compilation of CVs, like
> > PL_padix, PL_comppad_name, etc etc. At the start of compiling a CV, we
> > do SAVEI32(PL_cv_has_eval) and set it to 0. During the compile, we set 
> > it
> > to 1 if we discover any eval-like constructs. At the end of compiling 
> > the
> > CV, we check that whether it's got set, and if so, we pessimise any 
> > anon
> > CV's within scope. Thats all.
> >
> >
> 
> Aha,
> 
> So if we want to modify CVs later on, we just need o manually check if 
> any code below it would have turn on the cv_has_eval flag.

I think the whole scheme falls apart if CVs can get modified later
(ie if a CV without any eval-like ops suddenly acquires some).
Can this happen?

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

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About