Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:77306
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain the-echoplex.net from 208.113.200.129 cause and error)
MIME-Version: 1.0
In-Reply-To: <54E82419-931D-4F9E-8115-175EA1BDC970@darkrainfall.org>
References: <F3528124-17C4-4DB1-B11A-E9132775A144@ajf.me>
	<CAJF_ukW_rJjbzCHby4L71wAueBGRCfo4uOizWAxX6ngAHvdN0A@mail.gmail.com>
	<54E82419-931D-4F9E-8115-175EA1BDC970@darkrainfall.org>
Date: Thu, 18 Sep 2014 12:32:54 +0100
Message-ID: <CAKZZz6eGC6XH8WdDKL0V50bDZ3AE_8+J3HEjWPaNY40k8UTgGA@mail.gmail.com>
To: Gwynne Raskind <gwynne@darkrainfall.org>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=047d7bb708e07919ea050355584b
Subject: Re: [PHP-DEV] [RFC] Implicit isset() in Shorthand Ternary Operator
From: pete@the-echoplex.net (Pete Boere)

--047d7bb708e07919ea050355584b
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I'm seeing '??' as analogous to the way JS developers use '||', and I use
that all the time when writing JS.

Personally I wouldn't be interested in a function version because the
short-circuiting of '??' is an important distinction; not something you can
replicate with a function. Therefore having both would be confusing IMO.

Also, not much sure about a '??=3D', perhaps it should be a followup RFC
should '??' be accepted.



On 18 September 2014 10:26, Gwynne Raskind <gwynne@darkrainfall.org> wrote:

> On Sep 17, 2014, at 11:40, Matthew Fonda <mfonda@php.net> wrote:
> > Hi Andrea,
> >
> > This is great -- thanks to you and Nikita for the work here.
> >
> > Syntax wise, I would prefer a function-like syntax, e.g. coalesce($a, $=
b,
> > 'c') or ifsetor() instead of $a ?? $b ?? 'c'. I find this more readable=
,
> > and it avoids any possible confusion about precedence within the
> > expressions. Either way, still +1 for this feature.
> >
> > Best regards,
> > --Matthew
>
> I=E2=80=99m STRONGLY +1 in favor of this operator, ASAP; I=E2=80=99ve had=
 to write more
> than a few hacks to keep a large codebase I=E2=80=99m responsible from be=
ing a
> complete mess of isset() checks - 5.6 has saved me a lot of what used to =
be
> ugly workarounds (variadic functions anyone?), but this one still haunts =
me.
>
> I would argue for both coalesce() (as a language token) and ?? and ??=3D,=
 as
> shorthand forms, giving the user a choice as to which they find more
> readable. ?? is standard in both .NET and Apple=E2=80=99s Swift language =
- Apple
> added it to Swift (including the chaining behavior) early during the beta
> cycle due to user demand for exactly this kind of logic, and it=E2=80=99s=
 been part
> of C# for a long time.
>
> -- Gwynne Raskind
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>


--=20
Pete Boere
Web Developer

--047d7bb708e07919ea050355584b--