Re: [groovy-dev] advice needed

First of all you have to separate catch and finally. Syntetic return
in finally has no any useful meaning. If you want to return from
finally you do it explicitly. catch is another story.

On Mon, Jun 23, 2008 at 1:00 AM, Robert Fischer
<robert.fischer@...> wrote:
> If we *don't* have synthetic returns in catch statements, what would the result of this method call?
>
> def foo() {
>  try {
>    throw new RuntimeException()
>  } catch(Exception e) {
>  }
> }
>
> I'm inclined to being opposed to both try and catch/finally blocks because of flow-of-control
> problems like this: it's tricky to follow.  If you want a synthetic return, capture the return value
> and put it after the try/catch/finally.  Or use an explicit return.
>
> ~~ Robert.
>
> Andres Almiray wrote:
>> +1 on synthetic return in try
>> -1 on synthetic return on catch/finally
>>
>> reason being you write catch/finally because you expect something may go
>> wrong, so I believe you should be very careful in those code sections and
>> leave your expectations unambiguous, i.e., set your returns explicitly.
>>
>>