update: PadWalker is a bust, peek_sub and peek_our didn't return WARNING_BITS.

But Scope::Context looks like a candidate

update: another candidate Devel::Declare

> Devel::Declare

this is the ugly grandfather of pluggable keys, right?

Yes probably if I defined a key "case" I could implement it like this.

Unless mauke already published a switch module using Keyword::Simple ... ;)

See Switch::Plain

Cheers Rolf
_{(addicted to the Perl Programming Language and ☆☆☆☆ :)
Wikisyntax for the Monastery}

> Scope::Context

Thanks, interesting! :)

Seems to be based on Scope::Upper and does loads of black magic. (And might be useful to implement lisp style macros)

But only on upper contexts. The subs in questions are "lower" contexts

Cheers Rolf
_{(addicted to the Perl Programming Language and ☆☆☆☆ :)
Wikisyntax for the Monastery}

Magicky indeed, another one

Code::Splice - Injects the contents of one subroutine at a specified point elsewhere.

based on B::Generate - Create your own op trees.

I'm pretty sure PadWalker can't access global special vars inside a foreign sub.

And manipulating the warn handler looks cleaner now (though I have to check caller(2) too)

Cheers Rolf
_{(addicted to the Perl Programming Language and ☆☆☆☆ :)
Wikisyntax for the Monastery}