Far be it from me to discourage the use of warnings and strict. It's extremely disheartening to read in one of the responses from LanX that someone was ever fired for using them.
As you've pointed out, one aspect of this that I've found useful resorted to in very rare cases was to switch off warnings in only a certain part of a program in an enclosing block. This was almost always because of the "uninitialized" warning sounding off when it was irrelevant. I recall reading some CPAN code recently where the "once" warning was bothering a certain Matt Trout. (See the colorful language on line 95 of Moo.pm v 1.000007)
As for me, I can't think of a time when it would ever be apropos to disable strict or warnings completely.
--
Tommy
$ perl -MMIME::Base64 -e 'print decode_base64 "YWNlQHRvbW15YnV0bGVyLm1lCg=="'
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
