Mike Schilli wrote: > > While you're at it, here's my pipe dream: I want something like Dtrace, > where the logging framework zeroes out the opcodes that are currently > inactive, and the interpreter rushes through them at light speed with > practically no overhead. > > -- Mike >
This sounds like what I did with Log4perl::AutoCategorize, ( which is unsupportable - due to breakage of B::Generate ) FWIW, it hacked the optree to cause an AUTOLOAD fn to instantiate a different sub for every call-point. that new sub could be customized for to the way the config applied to that call-point, thus inlining all the config decisions. Assuming B::Generate comes back to life (there is hope yet), it will be practical to truly no-op the call. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ log4perl-devel mailing list log4perl-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/log4perl-devel
