Comments on: re: Java’s checked exceptions were a mistake http://madbean.com/2003/mb2003-15/ Your zero step program Sat, 22 Nov 2008 05:29:47 +0000 http://wordpress.org/?v=2.6.3 By: Malcolm Edgar http://madbean.com/2003/mb2003-15/#comment-32 Malcolm Edgar Tue, 27 May 2003 03:52:22 +0000 http://madbean.com/blog/2003-15#comment-32 <p>I am moving towards using unchecked exceptions after years of using checked exceptions for everything, except illegal arguments. The code is easier to read and write, and in most frameworks there is a top level exception handler which will do something sensible.</p> <p>I think when you have resources which must be cleaned up, such as Connections, I/O Streams and Files, you should use checked exceptions. Otherwise I think unchecked exceptions are fine, so long as you javadoc these in your methods. </p> <p>I find nesting causing the exceptions in very handy when designing exception handling code.</p> I am moving towards using unchecked exceptions after years of using checked exceptions for everything, except illegal arguments. The code is easier to read and write, and in most frameworks there is a top level exception handler which will do something sensible.

I think when you have resources which must be cleaned up, such as Connections, I/O Streams and Files, you should use checked exceptions. Otherwise I think unchecked exceptions are fine, so long as you javadoc these in your methods.

I find nesting causing the exceptions in very handy when designing exception handling code.

]]> By: Oliver Burn http://madbean.com/2003/mb2003-15/#comment-31 Oliver Burn Thu, 03 Apr 2003 06:25:00 +0000 http://madbean.com/blog/2003-15#comment-31 <p>That is an interesting approach using Generics. Just looking at the example convinces me that Generics will be taking the complexity of Java to a new level. This is good for people with big brains, and bad for the rest of us. It reminds me of my days in C++ using the templates.</p> <p>I guess Generics are like razor blades. A very efficient tool in the hands of an expert, but very dangerous in the hands of somebody who does not know what they are doing. Personally I am not desperately waiting for them.</p> <p>Out of curiosity, what if do not want my test() method to throw an exception. With the example it looks like I am forced to throw an exception. I guess I could use the RuntimeException, except your declaration says the exception must extend Exception?</p> That is an interesting approach using Generics. Just looking at the example convinces me that Generics will be taking the complexity of Java to a new level. This is good for people with big brains, and bad for the rest of us. It reminds me of my days in C++ using the templates.

I guess Generics are like razor blades. A very efficient tool in the hands of an expert, but very dangerous in the hands of somebody who does not know what they are doing. Personally I am not desperately waiting for them.

Out of curiosity, what if do not want my test() method to throw an exception. With the example it looks like I am forced to throw an exception. I guess I could use the RuntimeException, except your declaration says the exception must extend Exception?

]]>