🚀 go-pugleaf

dchamberlinNOSPAM@dlawton.com (Doug Chamberlin) writes:

> I just discovered what I feel is a strange behavior. I was debugging a
> Java program which had a "return true" statement inside a finally
> block of a method. The effect of this statement was to CANCEL then
> exception. That is, the method returned normally and did not propigate
> the thrown exception which was active upward in the call stack.
> 
> Anyone else see this behavior? it was totally unexpected by me!

It's to be expected: at the throw, it goes upwards, and finds a
finally block to execute. During this execution it performs a return,
and thus never gets to the "rethrow the exception after 'finally'"
step.

Place the return statement in the try block instead, the finally block
will execute regardless.