From: Andreas L. <av...@lo...> - 2008-12-12 12:52:58
|
On Fri, Dec 12, 2008 at 11:08:30AM +0200, Twylite wrote: > The counterpoints have already been presented. I think there are strong > arguments both ways, 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. That one isn't strong in my mind. Did I miss other arguments? (It would really surprise me, if implementation effort wasn't rather an argument *for* the "as ..."-clause instead of against, but I may of course be wrong there) > >Option #Omega: reinstate the "as"-clause. > try -mode tip329 ... > try -mode option1 ... > try -mode omega ... > C'mon, you know you want to ... ;> Nice revanche for my previous personal mix-up, (for which I apologized recently). I'm not the options-fancier. No, I honestly would not advocate any such options (not even with better names) > (Aside: we can still add the "as" clause later, if desired. I'd indeed desire that, on position 2 (right after #1: "also drop the per-handler variable lists"). Leaving it as in the TIP would be position 3, and no-"try"-at-all somewhere near 1000 followed only by -option'ed versions of "try". > There's also [catch] ...) Oh really? I thought that was being replaced... (just kidding :-) |