On Tue, May 15, 2012 at 04:44:02PM -0400, Eric Brine wrote: > On Tue, May 15, 2012 at 4:10 PM, Jesse Luehrs <doy@tozt.net> wrote: > > > No, I don't think that overriding 'catch' on its own makes sense either, > > for the same reasons I gave for 'else'. > > > > You said "else" should not be overridable. > I asked if "catch" should not be overridable. > You said "catch" should not be overridden. > > You're not answering my question. Or perhaps this implies you misspoke when > you talked about "else"? I'm trying to understand your position, but it's > very hard! Okay, now I'm confused. What are you actually asking? Are you referring to some potential future try/catch keyword that may be added to the language in the future? If you are, my position is that all of the arguments I've been making about 'else' apply equally well to 'catch', and they should be treated the same (i.e., not overridable via the keyword plugin mechanism). Is this what you're asking about? If not, what *are* you asking about? -doyThread Previous | Thread Next