[slf4j-dev] [Bug 110] Create a bridge between System.out/System.err and SLF4J

bugzilla-daemon at pixie.qos.ch bugzilla-daemon at pixie.qos.ch
Thu Apr 23 16:47:28 CEST 2009


http://bugzilla.slf4j.org/show_bug.cgi?id=110





--- Comment #6 from Ceki Gulcu <listid at qos.ch>  2009-04-23 16:47:27 ---
(In reply to comment #5)
> 
> That was why I rejected that approach - it seems to me that exceptions are the
> one thing you really don't want to swallow accidentally or attach incorrect
> timestamps to if nothing prints to the console for a significant period.

Agreed. How about a policy whereby exceptions are immediately copied on the
real console and also accumulated within the log buffer? We would have some
system.out and logging integration, without loosing whatever exceptions are
sent on the console...

> There's another less significant issue with it too - the contract of
> Throwable.printStacktrace says that the format of the printed stack trace
> depends on the implementation, so theoretically another Java implementer could
> output the trace in a format that would break this.  I'm less bothered about
> that, it's not like there are that many implementations out there and I'd
> hazard a guess they all copy Sun's format.

Agreed. 


-- 
Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the slf4j-dev mailing list