Actually, I have stuff like this littered throughout my code. When I'm developing, I need something to happen to tell me the if statement didn't execute. If the statement is something like this:
if ($foo) {
print LOG "Exit condition $foo reached.\n";
exit 0;
}
...then no big deal. If the code is more like this:
if ($line =~ /\w+sql=\w+/i) {
$db = "mysql";
$db_loc = (split(/=/, $line))[1];
}
...then during the testing period I need to account for a failure condition.
else {
print DEBUG "Error: Couldn't parse a database out of line ($line)\n
+";
}
In the field, I'd probably delete the error message, but there's a good chance that I'd leave the else statement in so I could re-enable it later if neccessary.
-Logan
"What do I want? I'm an American. I want more."
-
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.
|