Apoc 4: The skip keyword
Oh, one other tweak. The RFC proposes to overload next
to mean fall through to the next case. I don't think
this is wise, since we'll often want to use loop controls
within a switch statement. Instead, I think we should
use skip to do that. (To be read as Skip to the next
statement.)
I would like to suggest a different keyword that does not imply some
`jumping' action. For years, I have used `nobreak' in my C code when I want
to indicate that a case fall-through is intentional:
#define nobreak
switch(...) {
case 1: ...;
nobreak; /* intentional fall-through */
case 2: ...;
break;
case 3: ...;
}
Does anyone agree that `nobreak' reads much better than `skip'?
Dave.
Re: Apoc2 - STDIN concerns ::::: new mascot?
(apologies if this is a duplicate - I think my last post has gotten lost). The RFC pleads for a community spirit from ORA. Barring that, it seeks a new symbol for the community entirely I'd suggest a mongoose - eats poisonous snakes for breakfast. There's a sort of tie-in with Perl Mongers == Perl Mongoose as well :-) Dave.
Re: Apoc2 - STDIN concerns ::::: new mascot?
The RFC pleads for a community spirit from ORA. Barring that, it seeks a new symbol for the community entirely I'd suggest a mongoose - eats poisonous snakes for breakfast. There's a sort of tie-in with Perl Mongers == Perl Mongoose as well :-) Dave.
Another string concat proposal
What about using double-dot as the string concat operator: P5P6 -. . .. .=..= (or =.. for concat after) Many other operators already use doubled characters so this would not be an oddity for perl and it would leave single dot for all the things Larry wants it for without sacrificing the normal meanings of any of the other operators for concat. Dave Hartnoll.
Re: Another string concat proposal
On Wed, Apr 25, 2001 at 11:53:33AM +0100, Dave Hartnoll wrote: What about using double-dot as the string concat operator: P5P6 -. . .. .=..= (or =.. for concat after) You have missed a row for what the P5 .. operator becomes. And the ... operator [I am neutral as to whether using .. as concatenation is a good idea] Nicholas Clark That'll teach me to jump in without proper research. I had forgotten about the .. range operator and I wasn't even aware of the ... variety (I am now). I suppose it would be too cheeky to attempt to redeem myself by suggesting - as a range operator? (I would have suggested - but that introduces problems with it meaning the same as comma in some situations.) P5P6 -. . .. .=..= (or =.. for concat after) ..- ...- Another option I briefly considered for concat was .+ Perhaps too many changes overall, but food for thought for those without chronic indigestion already! Dave Hartnoll.
Re: Another string concat proposal
I wrote.. ..(I would have suggested - but that introduces problems with it meaning the same as comma in some situations.) Ignore that. I'm getting confused with = sometimes meaning the same as comma. I think I'll quit now before I dig myself any deeper :-) Dave.
Re: my and local
To my mind, things would be a lot clearer if my and local were to change places - but I can see why that would not be a good thing. If it's not too late for suggestions for renaming local, what about 'override'. Dave. - Original Message - From: "Michael Fowler" [EMAIL PROTECTED] To: "Tom Christiansen" [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Thursday, September 28, 2000 10:36 AM Subject: Re: my and local On Thu, Sep 28, 2000 at 10:18:34AM +0100, Tom Christiansen wrote: As we sneak under the wire here, I'm hoping someone has posted an RFC that alters the meaning of my/local. It's very hard to explain as is. my is fine, but local should be changed to something like "temporary" (yes, that is supposed to be annoying to type) or "dynamic". Someone has: RFC19 "Rename the Clocal operator" http://tmtowtdi.perl.org/rfc/19.pod Michael -- Administrator www.shoebox.net Programmer, System Administrator www.gallanttech.com --
