>On Tue, 1 Aug 2000 23:43:24 -0500, Jonathan Scott Duff <[EMAIL PROTECTED]> >wrote: >> (I, for one, support renaming local() to Something Better (if only I >> know what that was)) >how about clone()? I imagine that that name will be taken by something else, such as cloned interpreters. 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(). Oh, and we don't need dynamic(), because that's what our() does. One could even make Chip happy by allowing one to scopetemp a lexical. --tom
- RFC: lexical variables made default J. David Blackstone
- Re: RFC: lexical variables made default Jonathan Scott Duff
- Re: RFC: lexical variables made default Juanma Barranquero
- Re: RFC: lexical variables made default Michael Mathews
- Re: RFC: lexical variables made defau... Tom Christiansen
- Re: RFC: lexical variables made ... Jonathan Scott Duff
- Re: RFC: lexical variables m... Tom Christiansen
- Re: RFC: lexical variabl... Jonathan Scott Duff
- Re: RFC: lexical variables made ... Tad McClellan
- Re: RFC: lexical variables m... John Porter
- Re: lexical variables made default Jeremy Howard
- Re: lexical variables made default Ted Ashton
- Re: lexical variables made default Tom Christiansen
- Re: lexical variables made default Graham Barr
- RFC: lexical variables made default (revised) J. David Blackstone