----- Original Message ----- From: "Ceki Gülcü" <[EMAIL PROTECTED]> To: "Log4J Developers List" <[EMAIL PROTECTED]> Sent: Tuesday, June 11, 2002 12:28 PM Subject: Re: Binary compatibility between versions of log4j
> >How about this for a start. > > > >The API for retrieving a Category / Logger and the API for logging > >and checking whether logging is enabled should be fixed for all time. > >Code which is going to be used in a variety of different situations > >which are outside the control of the original author will probably > >not use any of the API. > >e.g. > > Create an interface, or an abstract class which both Category > > and Logger extend which defines the log (..) and is...Enabled (..) > > methods. [..] I agree. I think time comes for Log4j to become a framework (how many users are using Log4j in this way instead of a tipical library use? I mean, how many people have customized Log4j extending and implementing even if discouraged?) and preserve extension and backward compatibility in a more solid way. If some refactoring tecniques is needed, this is the time to think about for future releases. [...] > > Modify all previous and current versions of log4j to support that > > API. This may take a little while but it will allow new code and > > old code to coexist. No, this is not a workable way and is not really necessary. Best Regards, Giuseppe. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
