in reply to Locking PERL code another way

You'll need to keep in mind that some operations cause the optree to alter itself at runtime. First on my mind is the /o regex modifier (and maybe that's it for core perl). Maybe also tricks with B::Generate to alter the optree at "runtime" (considering that BEGIN, CHECK, INIT, runtime, and eval string are all different runtimes).

Replies are listed 'Best First'.
Re: Re: Locking PERL code another way
by Anonymous Monk on Sep 25, 2003 at 05:18 UTC
    So far we're using a nastily hacked version of Devel::OpProf.

    I take your other suggestions; we'd need to not allow them obviously, along with ``, eval etc and other neat things.
    Craig
[reply]

In Section Seekers of Perl Wisdom