comment on

Although you may miss the warnings (without FATAL), there's a 100% chance your customers will see them.

What kind of broad assumption are you making here? Lots of people work in environments where their customers come via a webserver. A webserver which logs the messages found on STDERR instead of sending them over the line to the customer.

My customers prefer a page that just does the right thing, instead of dying when Perl behaves like a toddler spotting a spider because it saw a comma inside a qw.

Warnings are warnings. Cases where Perl thinks, you're probably just right, and I will carry on, because, really, there's nothing actually holding me back, but just in case, you may want to look at this one of these days. Warnings most definitely are not errors. On errors, Perl dies. On warnings, it continues. Rightly so.

Now, for me, if there's anything I'd change about use warnings;, it's changing the use to a no. Or perhaps:

no warnings 'all';
use warnings 'uninitialized';
[download]

In reply to Re: Get stricter with use warnings FATAL => 'all'; by JavaFan
in thread Get stricter with use warnings FATAL => 'all'; by toolic

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


"be consistent"
	PerlMonks