In addition to what others have said:
  1. Your production code should not produce warnings. Generally speaking, if you have warnings, something is not right. Rather than trying to silence the warnings, you should heed what they say and fix the problem. Occasionally, in very rare cases, a certain command may cause a warning that is spurious but unavoidable. In that case, you can enclose just the offending command in a lexical block and silence the warnings there only (see below for example).

  2. You can redirect warnings so they aren't displayed to the user. It is understandable if you don't want the end user to see warnings or errors that your code produces. However, the better solution is to redirect warnings to where the user can't see them. That way, you still have access to them for debugging purposes if something goes wrong. See open for an example of redirecting STDERR to a file. If yours is a CGI program, CGI::Carp gives you flexible options for this. (And in a CGI program, warnings are not seen by the user anyway unless someone has explicitly directed them to the user).

Example: Disabling warnings for a single command.

{ no warnings; #Disable warnings for this block only spurious_warning_command(); }


When's the last time you used duct tape on a duct? --Larry Wall

In reply to Re: Disable Perl warning by ColonelPanic
in thread Disable Perl warning by nitai0

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.