Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

log::log4perl::resurrector(3pm) [debian man page]

Resurrector(3pm)					User Contributed Perl Documentation					  Resurrector(3pm)

NAME

       Log::Log4perl::Resurrector - Dark Magic to resurrect hidden L4p statements

DESCRIPTION

       Loading "use Log::Log4perl::Resurrector" causes subsequently loaded modules to have their hidden

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

       statements uncommented and therefore 'resurrected', i.e. activated.

       This allows for a module "Foobar.pm" to be written with Log4perl statements commented out and running at full speed in normal mode.  When
       loaded via

	   use Foobar;

       all hidden Log4perl statements will be ignored.

       However, if a script loads the module "Foobar" after loading "Log::Log4perl::Resurrector", as in

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

       then "Log::Log4perl::Resurrector" will have put a source filter in place that will extract all hidden Log4perl statements in "Foobar"
       before "Foobar" actually gets loaded.

       Therefore, "Foobar" will then behave as if the

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

       statements were actually written like

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

       and the module "Foobar" will indeed be Log4perl-enabled. Whether any activated Log4perl statement will actually trigger log messages, is up
       to the Log4perl configuration, of course.

       There's a startup cost to using "Log::Log4perl::Resurrector" (all subsequently loaded modules are examined) but once the compilation phase
       has finished, the perl program will run at full speed.

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

COPYRIGHT AND LICENSE

       Copyright 2002-2009 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.

perl v5.10.1							    2010-07-21							  Resurrector(3pm)

Check Out this Related Man Page

MDC(3)							User Contributed Perl Documentation						    MDC(3)

NAME

       Log::Log4perl::MDC - Mapped Diagnostic Context

DESCRIPTION

       Log::Log4perl allows loggers to maintain global thread-specific data, called the Nested Diagnostic Context (NDC) and Mapped Diagnostic
       Context (MDC).

       The MDC is a simple thread-specific hash table, in which the application can stuff values under certain keys and retrieve them later via
       the "%X{key}" placeholder in "Log::Log4perl::Layout::PatternLayout"s.

       Log::Log4perl::MDC->put($key, $value);
	   Store a value $value under key $key in the map.

       my $value = Log::Log4perl::MDC->get($key);
	   Retrieve the content of the map under the specified key.  Typically done by %X{key} in "Log::Log4perl::Layout::PatternLayout".  If no
	   value exists to the given key, "undef" is returned.

       my $text = Log::Log4perl::MDC->remove();
	   Delete all entries from the map.

       Log::Log4perl::MDC->get_context();
	   Returns a reference to the hash table.

       Please note that all of the methods above are class methods, there's no instances of this class. Since the thread model in perl 5.8.0 is
       "no shared data unless explicetly requested" the data structures used are just global (and therefore thread-specific).

COPYRIGHT AND LICENSE

       Copyright 2002-2009 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.

perl v5.12.1							    2010-02-07								    MDC(3)
Man Page