log4perl-devel

[log4perl-devel] easier interface

[Mathieu L. <mrd...@ya...>]

Couldn't the interface be simpler?

In order to write one line of log, here is what I need to
do:

	package Groceries::Food;
	use Log::Log4perl qw(get_logger);
	...
	my $logger = get_logger("Groceries::Food");
	...
	$logger->debug("New food: $what");

Shouldn't I just be allowed to do something like this:
	
	package Groceries::Food;
	use Log::Log4perl::EZ;
	...
	DEBUG("New food: $what"); # Or Debug() or debug()

In which case, the argument to get_logger() is guessed to
be the name of the current package.

I like the philosophy of the package, but calling
get_logger in every single functions that logs is just a
waste.

-Mathieu


__________________________________________________
Do you Yahoo!?
New DSL Internet Access from SBC & Yahoo!
http://sbc.yahoo.com

Re: [log4perl-devel] easier interface

[Kevin G. <ke...@go...>]

> I like the philosophy of the package, but calling
> get_logger in every single functions that logs is just a
> waste.

This is an emulation of a Java api--you were expecting terse and 
concise? ;-)

But seriously, if you don't want to call get_logger in every function, 
then don't--you could, for instance, make the logger a class variable:

use strict;
package Groceries::Food;

our $logger = Log::Log4perl::get_logger('Groceries::Food');

sub eat {
	$logger->debug("eating");
}
sub drink {
	$logger->debug("drinking");
}





-- 
Happy Trails . . .

Kevin M. Goess
(and Anne and Frank)
904 Carmel Ave.
Albany, CA  94706
(510) 525-5217