Re: [TCLCORE] TIP#329: Try/Catch/Finally syntax

[Twylite <tw...@cr...>]

Hi,
>> - removed the 'as {resultsVar optionsVar}' clause and introduced 
>> per-handler variable assignment
>>     
> An unfortunate decision that was rushed into the TIP just before voting.
> Three reasons against it:
>   
I was expecting this reply ;)

The counterpoints have already been presented.  I think there are strong 
arguments both ways, and I don't think either approach is a clear 
winner.   Per-handler variables was part of my original plan for the 
TIP; fall-through bodies wasn't.  Had the TCT not put their feature 
freeze at the crunch point of my two biggest projects I may have got the 
handling of "-" correct in the TIP ;)

> Option #2a:  make "-" be recognized in place of the variable list.
>   
Yes, definitely worth considering.  I think that Option #1 (use FOO's 
variable list and BAR's body) is unworkable.  Option #2 (BAR's list & 
body) leaves an unused variable list attached to FOO, which is just 
weird.  Either FOO's variable list must go away (require "-" if the body 
is "-") or both FOO and BAR's variables must be set (I don't know if 
this is somehow more useful).
> If a corrigendum was still possible, I'd prefer:
>
> Option #Omega:  reinstate the "as"-clause.
>   
try -mode tip329 ...
try -mode option1 ...
try -mode omega ...

C'mon, you know you want to ... ;>

(Aside: we can still add the "as" clause later, if desired.  It would be 
an optional clause between the try body and the first handler, and would 
not replace per-handler variable lists, but be set in addition to any 
variables in those lists.  There's also [catch] ...)

Twylite