On 2012-09-25 04:50, Gary Gregory wrote:
For SC, since you are recompiling, IMO, it is OK for a MAJOR release
to be different and print the stack trace.
It is just so nice to say debug(Throwable) and have the right thing
(IMO again) happen.
Having code say debug(throwable.toString(), throwable) is just... well
lame :(
I tend to agree. I have these same methods in my own internal logging
framework.
Perhaps if there were convenience methods like
void fatalException(Throwable t);
void debugException(Throwable t);
void warnException(Throwable t);
void infoException(Throwable t);
??
But then I like my API's to be quite wide, with lots of convenience
methods :-)
Disclaimer: http://www.peralex.com/disclaimer.html
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
