Hmmm, I can see some use in making warnings fatal, especially for debugging. But JavaFan's two replys are a good point: Harmless warnings should not kill production code. They could (and perhaps should) be logged, so errors can be debugged later.

Code will remain mostly without FATAL => 'all'. Except when you are debugging or a module author thinks that his code needs FATAL => 'all' enabled by default. But when you are debugging, you should not need to hack FATAL => 'all' into each and every file. There should be a way to force FATAL => 'all' from outside the code. Perhaps with a command line parameter or an environment variable. For extra bonus points, forcing FATAL => 'all' could be limited to a set of modules (list? regexp?).

Carp has a similar mechanism that you can enable by including -MCarp=verbose on the perl command line or in $ENV{'PERL5OPT'}. DBI has $ENV{'DBI_TRACE'}.

A simple-minded aproach could be ...

push @_,FATAL => 'all' if $ENV{'PERL_FATAL_WARNINGS'};

[download]

... as the first line in sub warnings::import. It would affect only code that use warnings. For more, perl will probably need some patches.

Alexander

--
Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)

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

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.