Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:102272
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.68 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <c3d7e2a7-2885-de03-4d84-cfaf0fe1f59d@gmail.com>
References: <CAESVnVqm3tVt53bQfxOpQcOMf_2fXhnu9y+42trTfv7zNMONHw@mail.gmail.com>
 <CAF+90c-HGB-2MbdrCYuQNrNYR4EJ9hAeFaKTW-sh1kwboDd0Kg@mail.gmail.com>
 <20180614155730.2C8BC1A8027C@dd1730.kasserver.com> <CAESVnVrbzLo1+hJ9RVgmGDeiZbMvCxfjxwf7-y1nK0J7O5qcyw@mail.gmail.com>
 <c3d7e2a7-2885-de03-4d84-cfaf0fe1f59d@gmail.com>
Date: Fri, 15 Jun 2018 09:40:27 +0100
Message-ID: <CALKiJKriPd5wucXuQSmy=S3dSJ-uaXav_H=ysxqMaW6sWwQAsQ@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000fa2842056eaa2af6"
Subject: Re: [PHP-DEV] Strict switch statements
From: rowan.collins@gmail.com (Rowan Collins)

--000000000000fa2842056eaa2af6
Content-Type: text/plain; charset="UTF-8"

On 14 June 2018 at 23:15, Stanislav Malyshev <smalyshev@gmail.com> wrote:

> Hi!
>
> > Would both be more apparent as to its meaning and leave the door open
> > for other uses.  Though at that point, tbqh, I think `switch ($a) use
> > (===) {...}` gives better visual isolation.
>
> I don't think we should reuse the use() thing for third purpose when
> we're already using it for two. I imagine with new parser logic we
> should not be as restricted in syntax choices as we've been before? So
> being a bit more explicit than "use(===)", which would be a bit of a
> head-scratcher for a casual PHP user. Something like "strict switch" at
> least gives a person something to ask about - what is "strict switch"
> exactly? But "use(===)" would be harder to read and harder to look up
> online.
>


As I've said before, I think precisely the opposite: === immediately means
"strict comparison" to anyone who knows PHP, but "strict switch" could mean
any number of restrictions: strict comparisons, no implicit fall-through of
cases, no duplicate cases, etc, etc

If it's the keyword reuse and punctuation that are an issue, what about
just picking a different word, and leaving out the parens:

switch ($foo) with === {
   case 42:
      blah();
   break;
   case '42':
       blerg();
   break;
}


Regards,
-- 
Rowan Collins
[IMSoP]

--000000000000fa2842056eaa2af6--