Well, it still only matters if it's invoked a *lot*, e.g. on the main
path of a Category or some appender or layout. *If* this is the case
then I would agree we should do something about it, although I don't
think it should be something as complete as log4j itself. Just moving
the check done in LogLog.debug, say, itself up to guard the invocation
would do it, e.g. change
LogLog.error(...);
to
if (!LogLog.quietMode) LogLog.error(...);
Anders
David Owens wrote:
>
> I agree, however, the code is always executed regardless of if the
> debugging actually results in output or not. So, as a result, you
> end up creating and concatinating Strings etc for no output.
>
> |)ave
>
> Anders Kristensen wrote:
>
> > LogLog is only intended to be invoked sparingly, e.g. during
> > configuration for debugging or when something goes wrong internally in
> > log4j. This means it doesn't have to be as fast as regular logging.
> >
> > Anders
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
