There's no point in removing strict, that is mostly a compile time check anyway; and if something really goes haywire, like using a hash entry as a reference (in a complex data structure) when it has already been assigned a string value, you don't really want it to go on. Without strict, Perl would use that string as the name for a global variable... Eventually it could even do serious damage to your data in the database.
As for warnings, that's something else. There have been numerous arguments about it, and there may be valid reasons to disable it in production code. The most important reason that suddenly warnings start to appear, is that an upgrade of Perl could make things that didn't produce a warning before, but do in the new Perl version. For a command line script, that is not so bad (on the contrary, in scripts for my own use they tend to point to irregular data), but if running on a web server, that suddenly could start to cause server errors. Ouch.
If anything, on a web server, make sure the warnings don't produce anything that the user sees, even if it doesn't cause an error. It's no use to him. Make them go to an error log.
-
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.
|
