>I feel strongly that "my" and "our" should both be renamed, >as well as "local". What then do you propose? my() and our() were chosen for their brevity. I might suggest that one look to Python's use of locals() and globals(). Currently, globals() is something like keys %{ __PACKAGE__ . "::"}, more or less, but locals() is unfindable from the Perl level. Perhaps this should be addressed. So too perhaps should the inconvenience/kludginess of the globals() solution above. Then again, I suppose that non-code-devel-tools folks seldom have cause to muck about in these waters. --tom
- 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
- Re: RFC: lexical variables made defau... skud
- Re: RFC: lexical variables made ... John Porter
- Re: RFC: lexical variables m... Tom Christiansen
- Re: RFC: lexical variables m... John Porter
- Re: RFC: lexical variables m... Piers Cawley