Re: [log4perl-devel] Change in behavior when upgrading to 1.26 and perl 5.10.0

2009-12-09 Thread Martin Evans
Mike Schilli wrote: > On Wed, 9 Dec 2009, Martin Evans wrote: > >> Since the upgrade we are getting no logging in one of the files we >> expected to get it. After a bit of searching around I discovered the >> module we were using was doing this: >> >> local

[log4perl-devel] Change in behavior when upgrading to 1.26 and perl 5.10.0

2009-12-09 Thread Martin Evans
Hi, I'm only sending this on the off chance someone here might be interested - I've sorted the problem out at my end. We've been using Log::Log4perl 1.25 and previous versions for ages but moved to a new development machine. The old one was perl 5.8.8 and Log::Log4perl 1.25 and the new one is per

Re: [log4perl-devel] Can caller_depth be set per logger

2008-02-08 Thread Martin Evans
Thanks for the reply Kevin. Kevin M. Goess wrote: > Martin, > > Have you tried something like this? It would go in each wrapper method > in your st.pm and db.pm, at the beginning of the method: > > local $Log::Log4perl::caller_depth = >$Log::Log4perl::caller_depth + 2;

[log4perl-devel] help with different caller depths

2007-12-03 Thread Martin Evans
Hi, I've used Log::Log4perl for some time (thanks) and also written DBIx::Log4perl but the caller_depth is now getting in my way and wondered what anyone else did. I have (as an example): program.pl - this uses Log::Log4perl to log at "myspace::myprogram" program.pl uses DBIx::Log4perl which l