Try-catch-finally-return clarification [duplicate]

by

If the return in the try block is reached, it transfers control to the finally block, and the function eventually returns normally (not a throw).

If an exception occurs, but then the code reaches a return from the catch block, control is transferred to the finally block and the function eventually returns normally (not a throw).

In your example, you have a return in the finally, and so regardless of what happens, the function will return 34, because finally has the final (if you will) word.

Although not covered in your example, this would be true even if you didn’t have the catch and if an exception were thrown in the try block and not caught. By doing a return from the finally block, you suppress the exception entirely. Consider:

public class FinallyReturn {
  public static final void main(String[] args) {
    System.out.println(foo(args));
  }

  private static int foo(String[] args) {
    try {
      int n = Integer.parseInt(args[0]);
      return n;
    }
    finally {
      return 42;
    }
  }
}

If you run that without supplying any arguments:

$ java FinallyReturn

…the code in foo throws an ArrayIndexOutOfBoundsException. But because the finally block does a return, that exception gets suppressed.

This is one reason why it’s best to avoid using return in finally.

More Related Contents:

  1. Multiple returns: Which one sets the final return value?
  2. Java Try Catch Finally blocks without Catch
  3. throws Exception in finally blocks
  4. NumberFormatException not wrking java
  5. How to return multiple objects from a Java method?
  6. “Missing return statement” within if / for / while
  7. Catching java.lang.OutOfMemoryError?
  8. Differences between System.out.println() and return in Java
  9. Is it expensive to use try-catch blocks even if an exception is never thrown?
  10. How do you implement a re-try-catch?
  11. Program freezes during Thread.sleep() and with Timer
  12. Does a finally block always run?
  13. Return a value from AsyncTask in Android [duplicate]
  14. Java if vs. try/catch overhead
  15. Java try/catch/finally best practices while acquiring/closing resources
  16. Java io ugly try-finally block
  17. EOFException – how to handle?
  18. Throws or try-catch
  19. Try-with-resources equivalent in Java 1.6
  20. Java try/catch performance, is it recommended to keep what is inside the try clause to a minimum?
  21. Try-with-resources and return statements in java
  22. Should try…catch go inside or outside a loop?
  23. Gets last digit of a number
  24. Why do we use finally blocks? [duplicate]
  25. Java – Does returning a value break a loop?
  26. Catching an exception that is nested into another exception
  27. Why is declaration required in Java’s try-with-resource
  28. Java InputMismatchException
  29. Strange finally behaviour? [duplicate]
  30. Try Catch Performance Java

Leave a Comment