Possible Duplicate:
“return” and “try-catch-finally” block evaluation in scala
There are two Scala functions:
a): def foo(): Int = try { 1 } finally { 2 }
b): def bar(): Int = try { return 1 } finally { return 2}
I cannot figure out why foo returns 1 but bar returns 2.
This behavior is explained in "Programming in Scala" by M.Odersky, L. Spoon and B.Venners. I have the first edition and section 7.5 (pg. 128) says:
it’s worth noting that Scala’s behavior differs from Java only because Java’s
try-finallydoes not result in a value. As in Java, if afinallyclause includes an explicit return statement, or throws an exception, that return value or exception will “overrule” any previous one that originated in the try block or one of its catch clauses. For example, given:
def f(): Int = try { return 1 } finally { return 2 }
calling f() results in 2. By contrast, given:
def g(): Int = try { 1 } finally { 2 }
calling g() results in 1. Both of these functions exhibit behavior that could surprise most programmers, thus it's usually best to avoid returning values from
finallyclauses.
Scala standard library has scala.util.control.Exception API that provides small functional library for handling exceptions. See the examples in scaladoc
The return statement of the finally block of bar() exits the method bar(). Therefor the result of the try block is not returned.
This example shows a (roughly) equivalent version of your methods foo() and bar():
object Test extends App {
def foo() = {
val result = { 1 }
{ 2 }
result
}
def bar(): Int = {
val result = { 1 }
{ return 2 }
result // this line is not processed
}
println("foo = " + foo()) // foo = 1
println("bar = " + bar()) // bar = 2
}
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With