Meh.
Not nagging at you personally obviously, but I've found that the use of strict and warnings to be more of a pain in the ass than anything generally useful or even pragmatic.. Yeah, I know, blasphemy. I'm far from a god of Perl, but, imho, if you willfully choose to carry the use strict boulder around your neck, you end up unnecessarrily doubling your development time chasing down bugs that aren't really bugs; It's time spent satisfying an unnecessary and optional hurdle, since the code already works as designed. I often wonder if half the stuff I do really justifies the time required to do it....For quickie scripts (like this one) I usually don't bother.
Doing something collaborative, however, or mission-critical production level stuff, would be a different story obviously. In those circumstances, i'd consider it useful.
Maybe i'm just resentful. :) Thanks for the writeup, anyhoo. :)
-
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.
|
