As often is the case there are two sides to each argument. This would not work for some code I use as warnings are often issued with warn() or Log::Log4perl::logwarn as a warning (something you should take notice of but it is not necessarily a code bug). If I just indiscriminately set warnigs are promoted to fatal a lot of code would stop working. This is partly where the Perl system of warnings breaks down. Warnings issued by Perl itself are probably worth knowing (and perhaps worth promoting to fatal so you can actually add code to cope with it) but application code can also call warn and in this case it probably means - take note - something to be aware of - but not necessarily fatal.
In reply to Re: Get stricter with use warnings FATAL => 'all';
by mje
in thread Get stricter with use warnings FATAL => 'all';
by toolic
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |