> Of course, but since the compiler no longer enforces it, they are easy to > miss and to ignore. I much prefer the compiler getting into my face to > remind me "this call can fail this way and that way, and you need to think > about this right now".
See that's what separates most developers. I definitely prefer the compiler NOT to get in my way and insist on holding my hand when it really is just a false sense of security! Remember, checked exceptions do not guarantee that you handle exceptional cases, they just require you to acknowledge them. The only true guard against exceptional cases, are unit tests. Otherwise, I'd much rather the problem gets allowed to bubble up to the surface where I can reason about it. There is simply no need to pollute method signatures and annoy the developer unnecessarily, luckily the remedy is simple: http://coffeecokeandcode.blogspot.com/2009/08/tweaking-javac-leniency.html -- 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.
