--On Thursday, May 12, 2005 11:42 AM -1000 Christoph Lofi <[EMAIL PROTECTED]> wrote:
Ah, ok, I know this topic gets annoying but I prefered the first solution. Why? Because there you can choose how what you use for linebreaks and you can make the method optionally formatting as html (long term goal: creating a better Code 400 Error Page).
Christoph
But Aaron's original method didn't implement any of that flexibility. Its stated goal was to create a string that mimiced as closely as possible the current printStackTrace behavior. Takuya's improvement does exactly that in a much more elegant way.
I do agree that Aaron's approach (but not his actual code) is better if you want to create a completely different presentation for stack traces (such as a "pretty" HTML version). To be honest, however, I kind of question the value of writing a bunch of code to prettify a stack trace. Will a "pretty" version actually save us any time during debugging? :-)
Cheers, Philip
