John Porter wrote: > It turns > out that 'my' having higher precedence than comma is signficantly > more useful than if it had a lower precedence. > Well, for me, it isn't useful, unless you can show me I'm wrong. At least give me an example that shows it's more useful this way. > Let's all just > acknowledge that fact, and move on. > Unless you show me why I should, I won't acknowledge it. It's easy to say ``It's better this way'' or ``It's been like this for a long time, it shouldn't change now''. Please just think about it and tell me in which cases `` 'my' having higher precedence than comma is signficantly more useful than if it had a lower precedence'', instead of just saying ``Let's all just acknowledge that fact''. I really can't find one way in which the current behaviour is more `useful'! - Branden
- Re: Closures and default lex... Nicholas Clark
- Re: Closures and default lexical... Branden
- Re: Closures and default lex... Bryan C . Warnock
- Re: Closures and default lex... Branden
- Re: Closures and default lex... Branden
- Re: Closures and default lex... Bryan C . Warnock
- Re: Closures and default lex... Branden
- Re: Closures and default lex... Bryan C . Warnock
- Re: Closures and default lex... Jonathan Scott Duff
- Re: Closures and default lex... John Porter
- Re: Closures and default lex... Branden
- Re: Closures and default lex... Branden
- Re: Closures and default lexical-scope fo... Randal L. Schwartz
- Re: Closures and default lexical-scop... Peter Scott
- Re: Closures and default lexical-scop... abigail
- Re: Closures and default lexical-scope fo... abigail
- Re: Closures and default lexical-scope for su... Branden
- Re: Closures and default lexical-scope fo... John Porter
- Re: Closures and default lexical-scope for subs David Grove
- Re: Closures and default lexical-scope for subs Branden
- The binding of "my" (Re: Closures and d... Nathan Wiger