RE: [log4perl-devel] log4perl and log4j

[Viner, D. <dv...@ya...>]

I'll look into what it takes to get info on logging.apache.org.  

what do you think about a couple of compatibility functions to support the
identical syntax ? e.g., :

sub isDebugEnabled { return shift->is_debug(); }


dave

-----Original Message-----
From: Mike Schilli [mailto:b2...@pe...] 
Sent: Sunday, March 28, 2004 1:20 AM
To: Viner David
Cc: Log4perl-Devel (log...@li...)
Subject: Re: [log4perl-devel] log4perl and log4j


Viner, David wrote on 3/26/2004, 10:59 AM:

 > I noticed in reading about log4j that it exposes slightly different
 > method
 > names than log4perl. for example,
 >
 > log4perl: is_debug()    log4j:  isDebugEnabled()
 > log4perl: is_info()     log4j:  isInfoEnabled()
 > log4perl: is_warn()     log4j:  _none_
 > log4perl: is_error()    log4j:  _none_
 > log4perl: is_fatal()    log4j:  _none_

The overall l4p goal is to be compatible with log4j, but there's some 
minor differences, especially when there's more perlish ways. The 
underscore notation vs. upper/lowercasing is something we used 
throughout l4p.

 > Also, we should look into how to get log4perl listed and linked to on
 > http://logging.apache.org/
 > Thoughts?

I got an invite on this, but I passed -- sounds like a lot of work. Are 
you volunteering?

-- 
-- Mike
Mike Schilli
m...@pe...