Perhaps I'm a little off base here, but are you really sure you are doing what you want to do? I can't think of any code that actually uses warnings::warn() at all, so I don't see why redefining it would be particularly useful. Redefining it won't affect CORE::warn, which you can only override through an import, and even then only within the scope of the module that does the use. (Healthy amounts of iirc here :-)
You can however intercept calls to warn via $SIG{__WARN__}, however this approach is a little strange and has potential problems playing well with other modules/code.
If this isnt the issue at hand then my apologies and Aristotles approach should do just fine. :-) (But an explanation of your underlying intentions would be welcome :-)
---In reply to Re: How to stack a call to a class method
by demerphq
in thread How to stack a call to a class method
by fokat
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |