Sub::Uplevel installs a CORE::GLOBAL::caller subroutine with a prototype that matches CORE::caller. Contextual::Return's CORE::GLOBAL::caller replacement has no prototype -- which is what causes the error if Contextual::Return loads after Sub::Uplevel.
I suspect you could load just Contextual::Return instead of your entire module before Test::Exception and it would work -- I guess replacing an unprototyped function with a prototyped one is not considered an error.
In my view, it's a bug in Contextual::Return, since you want to have the same caller() semantics as without a CORE::GLOBAL::caller override.
my $caller = caller @foo; # like "scalar @foo"
Yes, prototypes are evil, but core functions do have them, so CORE::GLOBAL replacements should have them as well for consistency.
-xdg
Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.
In reply to Re: Too much black magic
by xdg
in thread Too much black magic
by Tanktalus
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |