Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:100497
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain me.com designates 17.110.69.252 as permitted sender)
Date: Sun, 10 Sep 2017 11:42:16 +0200
To: internals@lists.php.net, Tony Marston <TonyMarston@hotmail.com>
Message-ID: <7cd2884a-6606-4c3f-8f95-776fd277878b@Spark>
In-reply-to: <7B.DB.10715.48405B95@pb1.pair.com>
References: <eb28362c-4f8f-45df-bbf0-582e8ad2b8af@Spark>
 <7B.DB.10715.48405B95@pb1.pair.com>
MIME-version: 1.0
Content-type: multipart/alternative; boundary=59b5096a_2ae8944a_17f67
Subject: Re: [PHP-DEV] Re: [RFC] Match expression
From: ilija.tovilo@me.com

--59b5096a_2ae8944a_17f67
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi Tony

> =E2=80=A6 you sometimes forget to insert a break=C2=A0statement then th=
at is your fault.

Any bug in your source code is ultimately your fault. But as mentioned be=
fore human error is inevitable. You can make it easier for your users to =
make less mistakes though. Other languages (e.g. Rust or Swift) have impl=
icit breaks in their switch statements. This has been done for a reason, =
I wouldn=E2=80=99t call this a non-issue.

> Millions of other programmers have no problem with the switch statement=


It=E2=80=99s all they know. They don=E2=80=99t complain about null pointe=
rs even though it=E2=80=99s inventor calls it his=C2=A0billion-dollar mis=
take. The customer rarely knows what he truly needs.

> they would not be pleased to have it changed just to deal with your=C2=A0=
perceived problem with it

I don=E2=80=99t suggest altering the behaviour of the switch statement bu=
t rather to introduce a new match statement.

Ilija


On 10 Sep 2017, 11:23 +0200, Tony Marston <TonyMarston=40hotmail.com>, wr=
ote:
> wrote in message news:eb28362c-4f8f-45df-bbf0-582e8ad2b8af=40Spark...
> >
> > Hi everybody=21
> >
> > Has this idea been discussed before=3F
> >
> > I find myself writing switch statements in PHP quite rarely. This has=
 a few
> > reasons:
> >
> > 1. It doesn=E2=80=99t have a =22strict=5Ftypes=E2=80=9D version
> > 2. It is quite verbose (lots of breaks)
> > 3. It is a statement rather than an expression
> >
> > Often, if / elseif statements turn out to be shorter, safer and easie=
r to
> > read than the switch statement.
> > What I=E2=80=99d really love is something like a match expression:
> >
>
> If there are circumstances where a series of if / elseif statements tur=
n out
> to be shorter, safer and easier to read than a switch statement, then t=
he
> intelligent thing to do would be to use if / elseif statements instead =
of
> trying to make the switch statement more complicated. If your problem w=
ith
> the switch statement is that you sometimes forget to insert a break
> statement then that is your fault. Try to use the language features as =
they
> were intended to be used and not how you would personally like to use t=
hem.
> Millions of other programmers have no problem with the switch statement=
, and
> they would not be pleased to have it changed just to deal with your
> perceived problem with it.
>
> --
> Tony Marston
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>

--59b5096a_2ae8944a_17f67--