incidentally, we also use the singleton pattern for our Log class - and use this instead of print - it adds PID, date, time etc to all the lines, manages the logging detail level - (error, warn, general, debug, dump)
And the Log has a DESTROY that gets called when the singleton instance is destroyed - ie at the end of program, were we do some tidy-up, including emailing our support group if any ERROR or WARNING messages were logged.
It also provides a logFatal() method, which logs a message, sends an email and does a POSIX::_exit($exitval)
HIH
The reason we use POSIX::_exit() is that we are running on *NIX with the buggy GCC 2.95 - a task that runs for 5 minutes, creating hashes of about 200MB takes 20-30 minutes for garbage collection - the POSIX::_exit() exits immediately.
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.