Beefy Boxes and Bandwidth Generously Provided by pair Networks
good chemistry is complicated,
and a little bit messy -LW

Re: Style guide for error messages?

by wazoox (Prior)
on Mar 09, 2006 at 17:18 UTC ( #535439=note: print w/replies, xml ) Need Help??

in reply to Style guide for error messages?

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/ line 96.

Log In?

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://535439]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others having an uproarious good time at the Monastery: (4)
As of 2023-01-29 08:51 GMT
Find Nodes?
    Voting Booth?

    No recent polls found