Resurrector(3)

πŸ’– NAME πŸ’–

Log::Log4perl::Resurrector β€” dark magic to resurrect hidden L4p statements πŸ§Ÿβ€β™€οΈβœ¨

Bestie, this is the Resurrector(3) page from the Log4perl crew β€” pull up a chair, we're bringing dead code back to life πŸŽ€


✨ DESCRIPTION ✨

Okay so picture this: you load use Log::Log4perl::Resurrector, and every module loaded after that gets its hidden statements uncommented and therefore 'resurrected', i.e. activated. Spooky? A little. Iconic? Absolutely πŸ’…

The hidden statements in question look like this:

###l4p use Log::Log4perl qw(:easy);

###l4p DEBUG(...)
###l4p INFO(...)
...

So this whole thing lets a module Foobar.pm be written with its Log4perl statements commented out, running at full speed in normal mode. When it gets loaded via

use Foobar;

all those hidden Log4perl statements just get ignored. Nothing to see here, move along πŸ¦‹

But β€” and this is the main character moment β€” if a script loads the module Foobar after loading Log::Log4perl::Resurrector, like this:

use Log::Log4perl::Resurrector;
use Foobar;

then Log::Log4perl::Resurrector will have put a source filter in place that extracts all the hidden Log4perl statements in Foobar before Foobar actually gets loaded. Sneaky. Genius. Obsessed 😭

So Foobar will then behave as if the

###l4p use Log::Log4perl qw(:easy);

###l4p DEBUG(...)
###l4p INFO(...)
...

statements were actually written like

use Log::Log4perl qw(:easy);

DEBUG(...)
INFO(...)
...

and the module Foobar will indeed be Log4perl-enabled. Slay 🌈

Heads up though: whether any activated Log4perl statement will actually trigger log messages is up to the Log4perl configuration, of course. That part is not our business πŸ’€

There's a startup cost to using Log::Log4perl::Resurrector β€” every module loaded afterwards gets examined, so it's doing a lil vibe check on all of them. But once the compilation phase has finished, the perl program will run at full speed πŸ”₯ No cap.

Some of the techniques used in this module have been stolen from the Acme::Incorporated CPAN module, written by chromatic. Long live CPAN! πŸ‘‘πŸ«Ά


πŸŽ€ LICENSE πŸŽ€

Copyright 2002-2013 by Mike Schilli <m@perlmeister.com> and Kevin Goess <cpan@goess.org>.

This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself. πŸ’œ


🌸 AUTHOR 🌸

Please contribute patches to the project on Github:

http://github.com/mschilli/log4perl

Send bug reports or requests for enhancements to the authors via our

MAILING LIST (questions, bug reports, suggestions/patches): log4perl-devel@lists.sourceforge.net

Authors (please contact them via the list above, not directly): Mike Schilli <m@perlmeister.com>, Kevin Goess <cpan@goess.org>

Contributors (in alphabetical order): Ateeq Altaf, Cory Bennett, Jens Berthold, Jeremy Bopp, Hutton Davidson, Chris R. Donnelly, Matisse Enzer, Hugh Esco, Anthony Foiani, James FitzGibbon, Carl Franks, Dennis Gregorovic, Andy Grundman, Paul Harrington, Alexander Hartmaier David Hull, Robert Jacobson, Jason Kohles, Jeff Macdonald, Markus Peter, Brett Rann, Peter Rabbitson, Erik Selberg, Aaron Straup Cope, Lars Thegler, David Viner, Mac Yang.


That's the whole page, bestie! πŸ“ This one's from perl v5.42.0, dated 2022-10-22 β€” go forth and resurrect some statements πŸ’–βœ¨πŸ§š

πŸ“¦ where this page comes from