If it helps at all, I develop software that runs on embedded systems like printers and factory robots. We develop in C, rather than Perl, but we not only have all build-time warnings turned up to maximum, but we won't accept any production code in which any warning occurs, for the same reasons as are mentioned above. We leave those on at all times, although the ASSERT macro does get commented out for release systems, but only because some of the tests take appreciable amounts of time.

For our systems as well as for Perl, having a log of user activity -- especially of any warnings generated -- is essential when bugs or problems occur. It's almost impossible to fix a bug if you can't reproduce it, and a good set of warning messages will let you do so. You may also want to dump your errors or warnings to a file rather than to the display, if a 'flawless' look is required for the user interface. On newer systems, we sometimes make the log file a rotating log -- it only retains the last 10 minutes' warnings (or whatever), but that's just to make it easier to manage a large volume of data. You shouldn't need that feature in a working system.

In reply to Re: Warnings and Strict in Production/Performance by Dervish
in thread Warnings and Strict in Production/Performance by deep submerge

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.