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.
-
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.
|