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."
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.