>I've heard "internal consistency" bandied about a lot. I think >auto-my()ing variables in these sub declarations is a bad idea. >What if you DON'T want them to be my()'ed? Do we have to add a global() >keyword? That's what Python requires. Keeping in mind that Python isn't truly block-scoped, but just global-package-function scoped, a variable without the global keyword belongs to whichever of those (package global or function local) it appears in. However, it's highly dodgy, because if used lvaluably, it is implicitly package global, but used rvaluably, it is implicitly function local. This is crazy. Someone (Sarathy?) mentioned that it's not always easy from a language level to tell which is which--so I wonder how Damian's want [rl]value thingawhatzitz will workie or not. --tom
- Re: RFC: lexical variables made defau... Jeremy Howard
- Re: RFC: lexical variables made ... Tom Christiansen
- Re: RFC: lexical variables m... Jeremy Howard
- Re: RFC: lexical variables made default (revi... Nathan Torkington
- Re: RFC: lexical variables made default (... Nathan Wiger
- Re: RFC: lexical variables made defau... Ariel Scolnicov
- Re: RFC: lexical variables made default (... Damian Conway
- Re: RFC: lexical variables made defau... Nathan Wiger
- Re: RFC: lexical variables made ... Johan Vromans
- Re: RFC: lexical variables m... Nathan Wiger
- Re: RFC: lexical variables m... Tom Christiansen
- Re: RFC: lexical variables made default (revi... J. David Blackstone
- Re: RFC: lexical variables made default (revi... Nick Ing-Simmons
- RE: RFC: lexical variables made default Ala Qumsieh
- Re: RFC: lexical variables made default John Porter
- Re: RFC: lexical variables made default Tom Christiansen
- Re: RFC: lexical variables made default John Porter
- Re: RFC: lexical variables made defau... Tom Christiansen
- Re: RFC: lexical variables made ... John Porter
- Re: RFC: lexical variables made defau... Peter Scott
- Re: RFC: lexical variables made ... John Porter