“Programs must be written for people to read, and only incidentally for machines to execute.” Abelson & Sussman, SICP, preface to the first edition Always aim for readable code. The key thing to remember is: Avoid try-catch in performance-critical functions, and loops Anywhere else they won’t do much harm. Use them wisely, use them when … Read more
In general, an exception should only be caught if it can actually be handled. It makes no sense to catch an exception for no purpose other than to log it. The exception is that exceptions should be caught at the “top level” so that it can be logged. All other code should allow exceptions to … Read more
Quoting the Java Language Specification, ยง11.2.3: It is a compile-time error if a catch clause can catch checked exception class E1 and it is not the case that the try block corresponding to the catch clause can throw a checked exception class that is a subclass or superclass of E1, unless E1 is Exception or … Read more
I use this as a general rule. Where it makes sense, use a pre-defined Java exception. For example, if your code has some sort of I/O Error, it is fine to throw an IOException. Only use exception hierarchies if you need to differentiate between the two exceptions in a try/catch block. A lot of times … Read more
Yes, it’s confusing. In Java, all program control paths of a non-void function must finish with a return, or throw an exception. That’s the rule put nice and simply. But, in an abomination, Java allows you to put an extra return in a finally block, which overrides any previously encountered return: try { return foo; … Read more
Is there really any point in adding a finally block here? The answer to this is a resounding “no”: putting a return statement in the finally block is a very bad idea. I just add the return null inside the catch block, which would execute the same behavior, or am I wrong? It wouldn’t match … Read more
Yes, this is a limitation in the exception handling logic. If a method contains more than one throw statement that throws an exception then you’ll get the line number of the last one that threw. This example code reproduces this behavior: using System; class Program { static void Main(string[] args) { try { Test(); } … Read more
Sure there is: put it at the bottom of the try block. try{ // something // i can do what i want here }catch(Exception e){ // handle exception } This is not entirely equivalent to your original code in the sense that if “what you want” throws, the exception will be caught locally (this would … Read more
Here are two ways: try { somethingThatMayThrowAnException(); somethingElseAfterwards(); } catch (…) { … } Or if you want your second block of code to be outside the try block: boolean success = false; try { somethingThatMayThrowAnException(); success = true; } catch (…) { … } if (success) { somethingElseAfterwards(); } You could also put the … Read more