> 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.
> 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.
(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
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.
> 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 th
out sacrificing the normal meanings of any of the other operators
for concat.
Dave Hartnoll.
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: "T
