Scott wrote: > On Wed, Aug 02, 2000 at 08:45:04AM -0600, Tom Christiansen wrote: > > Anything one chooses potentially conflicts with the user's > > namespace, but probably save() or temp() would be better, > > or even savetemp() or tempsave() or scopetemp(). > > How about deliver() or preserve()? How about contain() or detach() or revalue()? Also, how about renaming my() to local()? Will this be too confusing? --Ala
- 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
- Re: RFC: lexical variables made defau... skud
- Re: RFC: lexical variables made ... John Porter
- Re: RFC: lexical variables m... Tom Christiansen