Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:110709
MIME-Version: 1.0
References: <CAPyj-LB7jSiv+7DheaYpEcZXbjeJ9OMsRUTMOofnWbH4LyOQhA@mail.gmail.com>
 <CAPyj-LCV640AZpc=GPb2A+FxqWcSgnzzAH0VVLedCuM0RawmVQ@mail.gmail.com>
 <37f1f8fb-0e1b-cc39-f4b6-6c943a731d49@telia.com> <CAPyj-LAreEydWbK1JcBduQuDtu8r4Bv5a-Oma7mFkr3H2Y3y2A@mail.gmail.com>
 <250b7671-2919-9385-c149-931212397e4b@telia.com> <CAPyj-LDex6tQLp3HmCF6EitOcmBwuVb5ZiGuQsWWN0yUz09XwA@mail.gmail.com>
 <04d86e2d-0815-195a-6111-3034e0ca5918@telia.com> <CANeKSiQC1POTThpADpBHCZWeU8C4YhF3qR+OLEjXq35RKkQyKw@mail.gmail.com>
 <d7c5f55b-9c6f-c04a-15cd-0b66db10b57b@telia.com> <CAPyj-LB5FAkd2qL_ZE9sV13xzJVS7mJYO70O78YZ2c3yvY4DSg@mail.gmail.com>
 <f4c8eb78-fa5f-f4e8-9b58-b769a7af5442@telia.com>
In-Reply-To: <f4c8eb78-fa5f-f4e8-9b58-b769a7af5442@telia.com>
Date: Tue, 23 Jun 2020 13:09:12 +0100
Message-ID: <CALKiJKpBa6CoXi4xzmCg_j5DQmNy2kvAtu9ihmV00AyFd70drA@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000efc8f205a8bf3af3"
Subject: Re: [PHP-DEV] Re: [RFC][DISCUSSION] Match expression v2
From: rowan.collins@gmail.com (Rowan Tommins)

--000000000000efc8f205a8bf3af3
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tue, 23 Jun 2020 at 09:54, Bj=C3=B6rn Larsson <bjorn.x.larsson@telia.com=
>
wrote:

>
> Ok, thanks for the clarification. The reason for me to bring
> this up is that I was pondering on if this is the only place in
> PHP where a semicolon is required after a curly bracket
> when not used in an expression.
>


Two things:

- as proposed here, match is *always* an expression; it just happens that
PHP lets you throw away the result of an expression, so "match($x){};" is a
valid statement for the same reason "42;" is a valid statement
- as Ilija mentioned, ending a statement with an anonymous function also
leads to the combination "};"

function returnsFunc() {
    return function() { echo "Hello, world!\n"; };
}
function returnsMatchResult($x) {
    return match($x) { 1=3D> "Hello", 2=3D>"world" };
}


I'd also note that while there aren't currently many cases where it would
be ambiguous whether a statement or expression was intended, new ones might
be added in future. For instance, post-fix conditionals (like in Perl and
Ruby) would give us match($x) { ... } if $condition;

This kind of syntax short-cut tends to end up with complex rules of "it's
optional except when it's not", which I'm personally not a fan of.


Regards,
--=20
Rowan Tommins
[IMSoP]

--000000000000efc8f205a8bf3af3--