From: Martin E. <mar...@ea...> - 2008-02-07 17:16:19
|
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; I should have said I knew I could do this but a) there are an awful lot of methods b) when logging is not enabled each method has the overhead of the above statement for nothing. > It's a package variable, so no, there is no other way to set it per-logger. Shame. > There's some discussion of this in the FAQ ("perldoc Log::Log4perl::FAQ"). I haven't yet looked at the code - do you know how difficult it would be to make caller_depth per logger? Martin -- Martin J. Evans Easysoft Limited http://www.easysoft.com > Martin J. Evans wrote: >> Hi, >> >> I mailed this question some months ago and did not get any response so I >> thought I'd have one last go slightly reworded. >> >> I have many different loggers in the same application in the program >> itself and various modules. One module is a wrapper class around DBI and >> has to set the caller_depth to 2 but caller_depth seems to be global and >> hence this affects all other loggers in the same program. Is there any >> way to set caller_depth per logger? >> >> My precise example was in my post on this list 3-dec-07. >> >> Thanks >> >> Martin > > |