The stupid question is the question not asked | |
PerlMonks |
Warnings are enabled, but they aren't?by muthm (Acolyte) |
on Feb 27, 2023 at 09:25 UTC ( [id://11150629]=perlquestion: print w/replies, xml ) | Need Help?? |
muthm has asked for the wisdom of the Perl Monks concerning the following question: Hello wise monks. I was playing around with features and warnings because I would like to create my own Moose version that not only enables all warnings like Moose does (which is great), but also disables experimental::signatures warnings, because I don't want to repeat writing no warnings 'experimental::signatures'; over and over again. But my question is only about the strange and unexpected results that I get when I use warnings::enabled() for checking whether enabling and disabling warnings from my import sub works. In fact, for me it looks like warnings::enabled does not treat the enabled/disabled state of 'standard' warning categories like once or void correctly. I am sure there is a good explanation why the following code behaves as it does, and it would certainly help me if I understood why.
Thank you for a ration of your wisdom!
Back to
Seekers of Perl Wisdom
|
|