I've been working on a large project and using unit tests heavily.
I very much like the idea of Test::NoWarnings, except for two minor quibbles: So instead I opted to make all warnings fatal
package WarningsDie; use strict; use warnings; use Carp; # confess for warnings and death BEGIN { $SIG{__WARN__} = sub {confess $_[0]}; $SIG{__DIE__} = sub {confess $_[0]}; } 1;
and included this module in Test::Harness
$ENV{HARNESS_PERL_SWITCHES} = "-Iblah/blah/blah -MWarningsDie";
Every test and module starts with  use strict and  use warnings.

My meditation:

it is comforting to use the test suite to rid your modules of warnings; give it a try.

rkg


In reply to Die On Warnings by rkg

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.