Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:107557
MIME-Version: 1.0
References: <CAEsg9X0Tmkzxz9x2KgwNbPNdbmMz=a0J7Rt84Lh10W=3GQpRkA@mail.gmail.com>
 <CABdc3WqEzFV4ytrVtJB8OS2=3VMuNsHR7MqsTAHsg8-U==CkWA@mail.gmail.com>
 <CAP=w73X4sBBFtn=Z1OKfo0cdSZbd1-fst+5MFs5+8m2pEMxQew@mail.gmail.com>
 <CABdc3WpdXSCid0y4tizf8hoXUtSW+rqiDwk82ZGunNtp-ypytA@mail.gmail.com> <CAP=w73XE-ruRkPHwY777BctDaHDMFApzQBn8nCOtdkmW69GiWg@mail.gmail.com>
In-Reply-To: <CAP=w73XE-ruRkPHwY777BctDaHDMFApzQBn8nCOtdkmW69GiWg@mail.gmail.com>
Date: Wed, 16 Oct 2019 09:41:54 -0400
Message-ID: <CAPKYkKyx8bH_ARkGUFErWW-CsOAcQGgG+EC1TZjbEU6yxJxBJA@mail.gmail.com>
To: Kosit Supanyo <webdevxp.com@gmail.com>
Cc: =?UTF-8?Q?Micha=C5=82_Brzuchalski?= <michal.brzuchalski@gmail.com>, 
	PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000003f27d5059507440a"
Subject: Re: [PHP-DEV] Inline switch as alternative to nested inline conditional
From: chasepeeler@gmail.com (Chase Peeler)

--0000000000003f27d5059507440a
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wed, Oct 16, 2019 at 4:37 AM Kosit Supanyo <webdevxp.com@gmail.com>
wrote:

> I mean separation between cases not case conditions. Examples in your RFC
> uses semicolon as case separator instead of comma.
>
> <?php
> $say =3D switch (date("w")) {
>     case 0 =3D> "weekend!";
>     case 1, 2, 3, 4, 5 =3D> "weekday :(";
>     case 6 =3D> "weekend!";
> };
> echo "Today is {$say}";
>
> I prefer comma because semicolon should only be used to separate statemen=
ts
> but switch expression is list of condition/expression pairs not statement=
s.
> So it should be:
>
>  <?php
> $say =3D switch (date("w")) {
>     case 0 =3D> "weekend!",
>     case 1, 2, 3, 4, 5 =3D> "weekday :(",
>     case 6 =3D> "weekend!",
> };
> echo "Today is {$say}";
>
>
While using colons and semicolons would better sync up with current switch
syntax, I definitely like using arrows and commas better.

My only issue* is the fact that this introduces multiple ways to do the
same thing, which I thought was confusing and bad for new developers

*Not really an issue, just being a bit snarky. I actually love proposals
like this. It adds something useful to the language, people that don't like
it don't have to use it, and the positives outweigh the negatives in terms
of BC breaks (which are none, in this case, making it really easy to
outweigh them).

You may think t's fine because Java uses semicolon but IMO Java had made a
> mistake. (C# is semantically correct)
>
> Cheers
>
> On Wed, Oct 16, 2019 at 2:54 PM Micha=C5=82 Brzuchalski <
> michal.brzuchalski@gmail.com> wrote:
>
> > Hi Kosit,
> >
> > =C5=9Br., 16 pa=C5=BA 2019 o 09:41 Kosit Supanyo <webdevxp.com@gmail.co=
m>
> > napisa=C5=82(a):
> >
> >> Hi Michal
> >>
> >> I'had the idea similar to your RFC but instead of using `switch` keywo=
rd
> >> I think introducing `when` keyword is better. (as I know a language th=
at
> >> uses this keyword is Kotlin)
> >>
> >> $result =3D when ($v) {
> >>     'foo' =3D> 1,
> >>     'bar' =3D> 2,
> >>     'x', 'y', 'z' =3D> 3,
> >>     default =3D> null,
> >> };
> >>
> >> Above you can see that `when` syntax is more semantic than `switch`. A=
nd
> >> it is easier to implement in parser because it has no
> statement/expression
> >> ambiguity.
> >>
> >> But this might not be preferred by BC camps because introducing a new
> >> keyword might break BC.
> >> And if `switch` is chosen I still think the syntax should be comma
> >> separated instead of semicolon separated for consistency with other li=
st
> >> expressions (array/function call).
> >>
> >> $result =3D switch ($v) {
> >>     case 'foo' =3D> 1,
> >>     case 'bar' =3D> 2,
> >>     case 'x', 'y', 'x' =3D> 3,
> >>     default =3D> null,
> >> };
> >>
> >
> > That's exactly my proposal with commas, see here:
> >
> https://wiki.php.net/rfc/switch-expression-and-statement-improvement#swit=
ch_expression_introduction
> > Unfortunately, this RFC needs more work cause it mixes switch statement
> > enhancement with comma-separated list syntax and of switch statement - =
I
> > need to split it into two RFC's
> >
> > This is nice hearing that this idea has an interest.
> > As soon as the RFC will be split and finished I can start a discussion
> > thread.
> >
> > Cheers,
> > Micha=C5=82 Brzuchalski
> >
>


--=20
Chase Peeler
chasepeeler@gmail.com

--0000000000003f27d5059507440a--