It might be easier... but it is shorter.
Btw. In my 'solution' above I made a mistake that I just found as I was porting the script from my IDE (Komodo) to the server.
The undefined constant (debugging turned off) throws warnings about void constants. To get around this I used the following short fix:
# set DEBUGGING to the debug_switch value
use constant DEBUGGING => $debug_switch || 0;
Now to answer some questions...
Q: 'Why did I opt for the long version?'
A: It is clear and maintainable, even by persons with a minimum perl knowledge. I do this just to be nice to the people who have to live with my code.
Q: 'Why not use more than one level of debugging messages?'
A: I didn't need more than one. And knowing the application I doubt very much that this will change.
But... if I ever in need to use more than on level of debugging I will sure come back to this thread and look at the offered solutions for this feature.
thx /oliver
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.