Hi,

Warnings are important and should be kept. This is actually the first question I ask whenever a customer is confronted to ill CAD tool behavior (whether I actually coded it or not): "did you read (and hopefully understood) all warnings?"

Problem is, your issue seems to be of social engineering kind (i.e., fellow programmers are dead set against warnings) so I would first debunk their cons one by one (benchmarking is IMHO a very good idea) then quiet most or every warning. Of course, you can end up locally inserting 'no warnings' pragma into any dodgy code block you would not have time to properly analyze or refactor.

My 2 cents anyway...

Cheers,

Xavier

In reply to Re: Warnings and Strict in Production/Performance by maspalio
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.