Comments on: Why the Java compiler enforces catching some exceptions and not others http://steep.blogsome.com/2006/07/13/why-the-java-compiler-enforces-catching-some-exceptions-and-not-others/ Hayden Steep's development obstacle course. (Java, JEE, and beyond) Sat, 28 Nov 2009 05:05:30 +0000 http://wordpress.org/?v=1.5.1-alpha by: Don Shade http://steep.blogsome.com/2006/07/13/why-the-java-compiler-enforces-catching-some-exceptions-and-not-others/#comment-7 Wed, 19 Jul 2006 12:09:10 +0100 http://steep.blogsome.com/2006/07/13/why-the-java-compiler-enforces-catching-some-exceptions-and-not-others/#comment-7 Those very smart people seem to agree that checked exceptions are not needed. I'm not sure why (maybe I'm not as smart), but it seems to be a healthy reminder that Eclipse will force a try/catch block or a throws clause. If I were writing a database application and I knew there was a possible SQLException, I would write graceful handling code for this and a finally block for closing the connection to avoid connection pool leaks. But when it comes to file system exceptions (like file system full, etc.) there's not much I, as a Java programmer, want to do about this, so I would not "check" for those exceptions. My comments may seem trite. However, I've attended many Java User Group presentations where this topic is discussed and debated. Those very smart people seem to agree that checked exceptions are not needed. I’m not sure why (maybe I’m not as smart), but it seems to be a healthy reminder that Eclipse will force a try/catch block or a throws clause.

If I were writing a database application and I knew there was a possible SQLException, I would write graceful handling code for this and a finally block for closing the connection to avoid connection pool leaks.

But when it comes to file system exceptions (like file system full, etc.) there’s not much I, as a Java programmer, want to do about this, so I would not “check” for those exceptions.

My comments may seem trite. However, I’ve attended many Java User Group presentations where this topic is discussed and debated.

]]> by: Anon http://steep.blogsome.com/2006/07/13/why-the-java-compiler-enforces-catching-some-exceptions-and-not-others/#comment-6 Wed, 19 Jul 2006 05:08:38 +0100 http://steep.blogsome.com/2006/07/13/why-the-java-compiler-enforces-catching-some-exceptions-and-not-others/#comment-6 Checked exceptions are the bomb. They rule. Checked exceptions are the bomb. They rule.

]]> by: Hayden http://steep.blogsome.com/2006/07/13/why-the-java-compiler-enforces-catching-some-exceptions-and-not-others/#comment-5 Sat, 15 Jul 2006 14:51:32 +0100 http://steep.blogsome.com/2006/07/13/why-the-java-compiler-enforces-catching-some-exceptions-and-not-others/#comment-5 Thanks for the correction Tom. The only java.lang.errors I've experienced are OutOfMemory and StackOverflow. I didn't realize throwable had 2 branches. Thanks for the correction Tom. The only java.lang.errors I’ve experienced are OutOfMemory and StackOverflow. I didn’t realize throwable had 2 branches.

]]> by: Tom Hawtin http://steep.blogsome.com/2006/07/13/why-the-java-compiler-enforces-catching-some-exceptions-and-not-others/#comment-4 Sat, 15 Jul 2006 11:21:59 +0100 http://steep.blogsome.com/2006/07/13/why-the-java-compiler-enforces-catching-some-exceptions-and-not-others/#comment-4 Exceptions (with lower case e) that extend java.lang.Error are also unchecked. Exceptions (with lower case e) that extend java.lang.Error are also unchecked.

]]>