On Tue, 29 Aug 2000 16:41:41 -0600, Tom Christiansen <[EMAIL PROTECTED]> wrote:
> I've actually even used this at run-time, such as:
>
> $value = {
> azure => 0xF0,
> chartreuse => 0x7FFF00,
> lavender=> 0xE6E6FA,
> magenta => 0xFF00FF,
> turqu
> could a case operator be overloadable?
C isn't an operator, it's (half of) a control statement.
In a sense, the existing proposal already allows C to be "overloaded".
If your switch value is a subroutine, then the C value is passed
to that subroutine, which can then do...anything.
> I kn
TED]
sh.edu.au> cc:
Subject: Re: switch
s/statement/op
> I was thinking that the switch statement could possibly be expanded
> to also behave as an operator and not just a control statement.
I had considered this, but didn't put this in because no other
Perl control statements return a value. Personally, I like the
notion a great deal.
What th
>went through the archives about RFC22 "builtin switch statement".
>didn't see any mention of this, thought I'd throw it in there to see
>how it was recieved.
>I was thinking that the switch statement could possibly be expanded
>to also behave as an operator and not just a control statement.
>i.
went through the archives about RFC22 "builtin switch statement".
didn't see any mention of this, thought I'd throw it in there to see
how it was recieved.
I was thinking that the switch statement could possibly be expanded
to also behave as an operator and not just a control statement.
i.e. the
