Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:102728
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.41 as permitted sender)
MIME-Version: 1.0
References: <CAD2kNXBHTo5pJv3sYfEZjgCE6t8Nshv8=VoAesb+eamDhUVRpQ@mail.gmail.com>
 <CALKiJKrhZ-BCb8k4VPKgp=gGFxrUm9cEMo6TaCJsxCy+TZ+WCA@mail.gmail.com>
 <00c2c7a0-432e-0e19-983d-eca6c7cadf2e@gmx.de> <2123664.O6GaDqPnH7@vulcan>
 <CAJW__o116g8NmQnT+TRkTozqrS3Bhfw6gP+vj9vYeUnHrq6y7A@mail.gmail.com> <CAPhkiZy-s_Ua9ZzWFqdJu5DymqWd7C6dY+e0woLeps_cvcOOqA@mail.gmail.com>
In-Reply-To: <CAPhkiZy-s_Ua9ZzWFqdJu5DymqWd7C6dY+e0woLeps_cvcOOqA@mail.gmail.com>
Date: Tue, 10 Jul 2018 16:07:58 -0300
Message-ID: <CAEsg9X1GjSpEd8seC1qt0bd4DvAcpTUbKQ9y0nrFUiA5N9Bu=A@mail.gmail.com>
To: narf@devilix.net
Cc: Kalle Sommer Nielsen <kalle@php.net>, Larry Garfield <larry@garfieldtech.com>, 
	PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000d8c5ed0570a9d903"
Subject: Re: [PHP-DEV] Unifying logical operators
From: david.proweb@gmail.com (David Rodrigues)

--000000000000d8c5ed0570a9d903
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I think that "or" could be removed if PHP could supports inline
conditionals like:

die() if !$connected;
throw Exception() if fail();
$x =3D $y if (z() && w());

Or "when": die() when !$connected;

It seems more clear than $connected or die().

Em ter, 10 de jul de 2018 =C3=A0s 15:59, Andrey Andreev <narf@devilix.net>
escreveu:

> Hi,
>
> On Tue, Jul 10, 2018 at 9:37 PM, Kalle Sommer Nielsen <kalle@php.net>
> wrote:
> > Den tir. 10. jul. 2018 kl. 20.22 skrev Larry Garfield <
> larry@garfieldtech.com>:
> >> "do() or die()" code is/was very common in example code, tutorials, an=
d
> other
> >> intro material because it means you don't need to think about error
> handling.
> >
> > I personally wanted to extend this syntax but I never got around to it
> > to support: "do() or throw new Exception(...);", tho its just a code
> > style over: "if(!do()){ throw new Exception(...); }"
> >
>
> I sometimes declare a closure that throws an exception to do just
> that. It's very convenient in short(ish) scripts.
>
> isset($foo) OR $foo =3D 'bar'; (and similar variations using empty()
> and/or &&) is another pattern I use often to set fallback values for
> empty or missing inputs.
>
> An eventual deprecation would make literally all of my code output
> entire screens of warnings.
>
> Cheers,
> Andrey.
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--=20
David Rodrigues

--000000000000d8c5ed0570a9d903--