You really have to handle this on a case-by-case basis.

Warnings are certainly a great help in debugging code and finding potential bugs, and I have found *very* few times where an error was thrown without a good reason.

However, there are some cases where you are in an environment where you don't have a ton of control -- and maybe you are using a module that is a big help, yet throws a warning every time you use it. In that case, if the warnings bother you that much -- and you don't have access to fix the module, I'd say turn the warnings off.

Just use common sense, code/test/debug well, and all will be fine. Fear not... Your users will let you know when something goes wrong. :)

In reply to Re: Releasing code with warnings by joealba
in thread Releasing code with warnings by rir

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.