On 24/12/11 01:01, Mike Schilli wrote:
> On Mon, 21 Nov 2011, Martin J. Evans wrote:
>
>> Would you consider changing this? If not, I would be most grateful if
>> you could you point me at the place where I could change this
>> behaviour or tell my how I could override it.
>
> Alright, I gave in an
On Mon, 21 Nov 2011, Martin J. Evans wrote:
> Would you consider changing this? If not, I would be most grateful if
> you could you point me at the place where I could change this
> behaviour or tell my how I could override it.
Alright, I gave in and fixed it :)
https://github.com/mschilli/log4p
On 21/11/11 04:46, Mike Schilli wrote:
> On Tue, 1 Nov 2011, Martin J. Evans wrote:
>
>> So substituting warn with logwarn does not always warn!
>
> That's an interesting case. The way it's implemented right now is that
> logwarn() will only call warn() (along with other log4perl actions) if
> the
On Tue, 1 Nov 2011, Martin J. Evans wrote:
> So substituting warn with logwarn does not always warn!
That's an interesting case. The way it's implemented right now is that
logwarn() will only call warn() (along with other log4perl actions) if
the log level is greater or equal than WARN.
logdie()
Hi,
Is this really the intended behaviour:
perl -w -le 'use strict;use warnings;use Log::Log4perl qw(get_logger); my $lh =
get_logger("BET::Data::Remove"); $lh->debug("fred");$lh->logwarn("warning from
l:l"); warn("warning");'
Log4perl: Seems like no initialization happened. Forgot to call ini
