On Fri, 28 Feb 2014, Dave Pointon wrote: > whilst developing a bespoke package that uses L4P indirectly (it > 'use's a package that 'use's a package to try and subclass L4P), I was > seeing a carp message that pointed to the 'use' statement
Actually, the register_wrapper() call should take care of that problem: http://search.cpan.org/dist/Log-Log4perl/lib/Log/Log4perl.pm#Using_Log::Log4perl_with_wrapper_functions_and_classes If not, do you have a short code example to illustrate the problem? > My enhancement would be to select e.g. via an environment or package > variable, whether carp or cluck is used to generate any warnings in > order to facilitate problem resolution. That'd be a nice addition to Carp.pm :). -- -- Mike Mike Schilli m...@perlmeister.com ------------------------------------------------------------------------------ Flow-based real-time traffic analytics software. Cisco certified tool. Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer Customize your own dashboards, set traffic alerts and generate reports. Network behavioral analysis & security monitoring. All-in-one tool. http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk _______________________________________________ log4perl-devel mailing list log4perl-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/log4perl-devel