Another pitfall may or may not be the == 0. Is it
meant to test falseness? If so, it is
not precise. Perl understands the notion of an
undefined value, which is not the
same as zero, so this test is broken if it
means to check falseness.
Well, accutally.... it's true that undefined is not the
"same" as zero, but they are numericly equal. As you
can see, it generates a warning, but it does evaluate to true...
laptop:~> perl -wle 'print "TrUe" if undef == 0'
Use of uninitialized value in numeric eq (==) at -e line 1.
TrUe
A better example as to why you wouldn't want to use
"$status == 0" as a test for truth is non numeric strings.
the string "foo" is true, but it is numericly equal to 0...
laptop:~> perl -le 'print "TrUe" if "foo" == 0'
TrUe
laptop:~> perl -le 'print "TrUe" if "foo"'
TrUe
-
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.
|
