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.
Having done a bit of C# development where exceptions are not checked there were some times when I missed them. One of my coworkers tended to be quite sloppy / blasé about catching exceptions in code and sometimes it would have been good to know what my program might need to handle. The check exceptions in Java can be seen as part of the documentation. I was caught out at least once when an exception was thrown by a library which was being used but the specific exception was not mentioned in the documentation as being potentially thrown. I know that this was a documentation issue but still, I think checked exceptions help me be more aware of what things I need to handle without having to keep referring to the documentation. -- 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.
