I currently use a logging object I wrote to manage messages. When something's going wrong, my rule of the thumb is to write the message to the log object, then to return undef. something like :
use strict;
use warnings;
package bozo;
use Message;
sub failing {
my $log = Message->new ;
$log->set_error("this always fails");
return
}
package main;
use Message;
my $log = Message->new ;
# I sometimes do this
eval { `touch /toto` };
if ($@) { $log->set_error("it failed! : $@") ;
# or this
if ( not 0 ) {
$log->set_error("it failed too!")
}
# now calling the failing sub up there:
if ( not bozo::failing() ) {
print $log->get_message();
}
Whatever I do with the error string, the Message object also spits out errors and messages to the log, this way (PID, date and time, the the message):
[25435] 2006-02-21 14:27:20 : ERROR : DBD::Pg::st execute failed: exec
+ute on disconnected handle at ../lib/Archiver/Job.pm line 96.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Outside of code tags, you may need to use entities for some characters:
| |
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.
|
|