The reason is that errors which are by definition rare events, do not need to be performance sensitive. I hope that helps,
At 11:00 29.10.2002 +0100, you wrote:
Hi I am using log4j at work (building a network simulator mostly) and was wondering how it could perform in a game development project. Regarding performance, it seem obvious to use the Logger.isDebugEnabled() and such before logging any event. But why is there only such a method for DEBUG and INFO ? I am pretty sure there is a reason for not having isWarningEnabled(), isErrorEnabled(), and isFatalEnabled() but I cannot see which... Could you please enlighten me on this point ?Regards Herve
-- Ceki TCP implementations will follow a general principle of robustness: be conservative in what you do, be liberal in what you accept from others. -- Jon Postel, RFC 793 -- To unsubscribe, e-mail: <mailto:log4j-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:log4j-dev-help@;jakarta.apache.org>
