On Mon, Mar 28, 2011 at 1:31 PM, Kevin Wright <[email protected]>wrote: > > > This is the problem causing Java's excessive stack traces, just exemplified > by Spring more than most other libraries/frameworks: > http://steve-yegge.blogspot.com/2006/03/execution-in-kingdom-of-nouns.html > >
I like Steve's articles but could you at least be more specific than quoting a ten page blog post? > > The "best technique" to solve this arguably isn't checked exceptions. It's > true alternate return values coupled with a decent implementation of > closures to pull much of the boilerplate out of those stack traces. > We have rebutted this claim of yours many, many times. Your proposal is completely missing the non local handling aspect of exceptions. I am baffled why you keep thinking that return values (even alternate ones) are even in the same league as exceptions when it comes to handling errors. It's a lesson we learned in the early 90's. -- Cédric -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
