Beefy Boxes and Bandwidth Generously Provided by pair Networks
"be consistent"

Re: Log::Log4perl syslog wall best practice

by polettix (Vicar)
on Mar 20, 2012 at 07:36 UTC ( #960543=note: print w/replies, xml ) Need Help??

in reply to Log::Log4perl syslog wall best practice

After having looked at the explanation in the RT thread, I'd say that you can go for this small function:
sub ERRORDIE { Log::Log4perl->get_logger->error_die(@_); }
Put that in a module, use where applicable and you should be set without much complaining from cow-orkers.

The fact is that you're trying to use the same hammer for very different nails, so you either need a different hammer (e.g. ERRORDIE above) or substitute the hammer on the fly (e.g. redefine LOGDIE/LOGCROAK/LOGEXIT). Personally, I'd leave LOGDIE its advertised semantic - i.e. raise a FATAL log message and exit with an error - and use a different function (e.g. ERRORDIE above) to do similar but different things.

perl -ple'$_=reverse' <<<ti.xittelop@oivalf

Io ho capito... ma tu che hai detto?

Log In?

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

How do I use this? | Other CB clients
Other Users?
Others taking refuge in the Monastery: (8)
As of 2016-10-26 09:18 GMT
Find Nodes?
    Voting Booth?
    How many different varieties (color, size, etc) of socks do you have in your sock drawer?

    Results (338 votes). Check out past polls.