From: Andreas L. <av...@lo...> - 2008-12-13 18:49:07
|
Joe English <jen...@fl...> wrote: > Andreas Leitgeb wrote: > > I'm definitely biased, but the only argument for handler-specific > > variables, that I found in the discussion was that all the other > > languages (especially Java) have per-handler variables. > Specific example: Twylite already answered my question, and he also gave better reasons than that one, so I declared my defeat on this topic already. ;-) > At point (3), you know that $xxx and $opts are set to _something_, > but you don't know what. You usually don't care, either. Without the intention to reopen the discussion, with per handler variable lists, not only do I not know what a variable really contains (error-message or return-value), but also don't know which variables were actually set in the try. PS: I'd have called the variable "retval" or just "rv" instead of "xxx" and would probably do so if an "as ..." clause is ever added as optional clause, later. PPS: most of the cases, I'd place the "on ok"-body right into the try-body, so the different interpretation of the variable would not be a problem most of the times. |