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/log4perl/commit/7d7fbbb45254d6c903f5b3cb91d7 Thanks for bringing this to my attention. Please give it a whirl! -- -- Mike > > Martin > >>> 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 init()? >>> warning at -e line 1. >>> >>> i.e., if something does not call init for Log::Log4perl but has a log >>> handle when logwarn is called a warn does not happen? >>> >> >>> >>> I spent some time debugging a problem this morning only to discover this. I >>> find this most worrying as I'd expect the warn to happen whatever. If you >>> substitute logdie for die it seems to work. >>> >>> perl -MLog::Log4perl -le 'print $Log::Log4perl::VERSION;' >>> 1.33 >>> This is perl, v5.10.1 (*) built for i686-linux-gnu-thread-multi >>> >>> Martin >>> > > > -- -- Mike Mike Schilli m...@perlmeister.com ------------------------------------------------------------------------------ Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev _______________________________________________ log4perl-devel mailing list log4perl-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/log4perl-devel
