I'll send you a postcard! :)
> Anyway, I'm probably boring everybody now.
not me! :)
Also because a week ago I started using exactly these closed_over features of PadWalker and this worries me a little.
what does "when the coderef is hit at run-time" exactly mean?
Lets say
a) I use B::Deparse to deparse and reeval the body of a named sub in a phase before runtime (e.g. CHECK)
b) the function has "normal" closed-over variables, i.e. not depending on run-time variables like from a for-loop.
Do I risk that PadWalker gets it wrong if I transfer the closed-over vars from old to new sub?
Cheers Rolf
( addicted to the Perl Programming Language)
In reply to Re^4: Silencing specific warnings when executing coderef?
by LanX
in thread Silencing specific warnings when executing coderef?
by LanX
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |