On Mar 24, 4:44 pm, Carl Jokl <[email protected]> wrote: > Another aspect of dropping exceptions is the lost of the stack trace. > A good stack trace is very useful in establishing what went wrong and > where in a program.
Hmm but to be honest, many other programming languages prior to Java were far better at pinpointing the *actual* problem. In a modern Java stack you have warning and errors thrown left and right, and uber- frameworks like Spring generate stack-traces you can actually see from space! > Having done a bit of C# development where exceptions are not checked > there were some times when I missed them. The full story is that the designers of C# were not convinced that they were worth the trouble. Indeed on the .NET platform you can opt- in using code contracts which goes far beyond checking failure invariants (which is all a checked exception is). [http:// blogs.msdn.com/b/bclteam/archive/2008/11/11/introduction-to-code- contracts-melitta-andersen.aspx] -- 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.
