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

Re: [PATCH] jumbo closure fix

Thread Previous | Thread Next
From:
A Bergman
Date:
February 27, 2003 06:35
Subject:
Re: [PATCH] jumbo closure fix
Message ID:
9F3F0242-4A60-11D7-BB15-003065D64CBE@nanisky.com

On torsdag, feb 27, 2003, at 14:20 Europe/Stockholm, Dave Mitchell 
wrote:

>
> 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?
>
>

Of course this can happen, everything can always happen, the only way 
to stop it from happening is keeping the memory storing the cv in a 
safe/locked non networked compartment  on the bottom of the sea (far 
away from the likes of me and Simon :-). However don't let that stop 
the scheme, all kinds of nasty XS hacks and B::Generate/optimize hacks 
need to to do the correct thing, which is rewrite the CVs optree and 
set the right flags or not add any eval like ops.

Arthur


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