Hmmm, I guess not. At least, I couldn't get 'no overload' to do anything
useful.
How much of a PITA is it to use overload::StrVal and overload::Overloaded in Devel::StackTrace?
Not a PITA at all, I just liked the other solution even more.
This is from the overload docs:
Run-time Overloading
Since all "use" directives are executed at compile-time, the only way
to change overloading during run-time is to
eval 'use overload "+" => \&addmethod';
You can also use
eval 'no overload "+", "--", "<="';
though the use of these constructs during run-time is questionable.
So perhaps the eval will do the trick, esp. since one is generally generating a stack trace just before die'ing, so the run-time use of these constructs is not so questionable.
Regards,
David
