Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:100489
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain basereality.com from 209.85.192.176 cause and error)
MIME-Version: 1.0
In-Reply-To: <87.77.10715.B5AD3B95@pb1.pair.com>
References: <eb28362c-4f8f-45df-bbf0-582e8ad2b8af@Spark> <87.77.10715.B5AD3B95@pb1.pair.com>
Date: Sat, 9 Sep 2017 13:18:04 +0100
Message-ID: <CA+kxMuRr0nk3UUKsWpr7iFpCq2cYUq5Rh6UV6o-gHWC8kN3=6g@mail.gmail.com>
To: Andreas Treichel <gmblar@gmail.com>, Ilija Tovilo <ilija.tovilo@me.com>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Re: [RFC] Match expression
From: danack@basereality.com (Dan Ackroyd)

On 9 September 2017 at 12:21,  <ilija.tovilo@me.com> wrote:
> Hi everybody!
>
> Has this idea been discussed before?
> ..
> Each case has an implicit `break`

This part has come up before, as the default behaviour of fall through
is a nasty gotcha for when you forget to put break. I can't find the
conversation right now, but the discussion was around a 'select'
keyword. I think the conversation didn't proceed as it seemed like
adding a new keyword just to fix the fall-through behaviour was a bad
tradeoff.

This RFC idea adds more capabilities, so is a better trade-off, and
more likely to be worth doing in my opinion.

> One downside, since PHP doesn=E2=80=99t implicitly return the last statem=
ent
> as some languages do there=E2=80=99s no obvious way to do multi-statement=
 cases.

People are still working on and hoping for short-closures. That RFC
and any potential one for this, should attempt to use the same syntax.


On 9 September 2017 at 13:11, Andreas Treichel <gmblar@gmail.com> wrote:
> Something like:
>
> *wall_of_hard_to_read_code*

Yeah, that's a pretty good example of why I'd be in favour of this RFC.


cheers
Dan
Ack