Branden wrote: > Anyway, I don't see why `local' (and `our' and `my') should bind more > strongly than , and = . They are list operators, they should behave > the same as those. "In general, perl does what you want -- unless what you want is consistency." The point is that consistency is NOT the overarching goal of perl's design; being useful to the programmer is. It turns out that 'my' having higher precedence than comma is signficantly more useful than if it had a lower precedence. Let's all just acknowledge that fact, and move on. -- John Porter Ann wenno haddum billizac...
- Re: Closures and default lex... 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