Re: RFC: Rename local() operator

2000-08-07 Thread Piers Cawley
Nathan Wiger [EMAIL PROTECTED] writes: But it isn't "here" that's the problem. If we just wanted to change the value "here", we could use my(). The problem is that local() changes the value for somewhere else as well as here. Well, as has been pointed out, special^Wlocalized

Re: RFC: Rename local() operator

2000-08-06 Thread Nathan Wiger
shadow $/ = "\n"; seems to have the right implications to me. Personally, I like this by far out of all the suggestions I've heard. "save" seems to say "save THIS value" (the one you're setting, not the global one you can't see). "hide" is a little too general (hide what in what?). But I

Re: RFC: Rename local() operator

2000-08-06 Thread Buddha Buck
What about Chide ? Here's yet another one - how about "here"? { here $/ = "\n"; # what it is in here } Not really any confusion on this - $/ is "\n" 'in here', but maybe something else outside. Unlike "hide" or others, this doesn't connote it's necessarily any

Re: RFC: Rename local() operator

2000-08-06 Thread Peter Scott
At 12:50 AM 8/7/00 -0500, Jonathan Scott Duff wrote: On Sun, Aug 06, 2000 at 08:03:51PM -0700, Nathan Wiger wrote: What about Chide ? Here's yet another one - how about "here"? Doesn't this have a list of its own yet? Well, "here" isn't a verb and I think we need a verb er ... here.

Re: RFC: Rename local() operator

2000-08-05 Thread Bart Lateur
On Fri, 4 Aug 2000 10:54:16 -0500, Jonathan Scott Duff wrote: Csave If I had my druthers, save() would be it. I'm against it. Why? Because it suggests that all it does is save the value for later retrieval. It does not: the value is cleared as well. It masks the previous global value, as if

Re: RFC: Rename local() operator

2000-08-05 Thread Jonathan Scott Duff
On Sat, Aug 05, 2000 at 12:04:30PM +0200, Bart Lateur wrote: On Fri, 4 Aug 2000 10:54:16 -0500, Jonathan Scott Duff wrote: Csave If I had my druthers, save() would be it. I'm against it. Why? Because it suggests that all it does is save the value for later retrieval. It does not: the

Re: RFC: Rename local() operator

2000-08-05 Thread Russ Allbery
Nick Ing-Simmons [EMAIL PROTECTED] writes: What about Chide ? I think Cproxy or Cdeputy has merit - "while I am out contact ...". But I still think Csave is the essence of what it does. I like either Chide or Csave too, but just to throw out the other idea that occurred to me, what's being

Re: RFC: Rename local() operator

2000-08-05 Thread Chaim Frenkel
guard protect Hmm, 'guard' is just as long as 'local'. chaim "JSD" == Jonathan Scott Duff [EMAIL PROTECTED] writes: JSD More words: JSDstore() # put away for the duration of the scope JSDtuck() # Now I lay me down to sleep JSDhide()

RFC: Rename local() operator

2000-08-04 Thread J. David Blackstone
Since no one else has taken this up, I'll start an initial draft. =head1 TITLE Rename the Clocal operator =head1 VERSION Maintainer: J. David Blackstone [EMAIL PROTECTED] Date: 4 Aug 2000 Version: 1 Mailing List: [EMAIL PROTECTED] Number: not yet assigned =head1 ABSTRACT The

Re: RFC: Rename local() operator

2000-08-04 Thread skud
Please do not send your RFCs to both perl6-rfc and perl6-$working_group. The RFC librarian will automatically forward your RFC with a number on it, which is kinda neater. K. -- Kirrily Robert -- [EMAIL PROTECTED] -- http://netizen.com.au/ Open Source development, consulting and solutions Level

Re: RFC: Rename local() operator

2000-08-04 Thread Jonathan Scott Duff
On Fri, Aug 04, 2000 at 01:37:09AM -0500, J. David Blackstone wrote: =head1 IMPLEMENTATION Csave If I had my druthers, save() would be it. -Scott -- Jonathan Scott Duff [EMAIL PROTECTED]