Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:91899
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.45 as permitted sender)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
In-Reply-To: <56F40965.30302@telia.com>
Date: Thu, 24 Mar 2016 16:46:35 +0100
Cc: Andrea Faulds <ajf@ajf.me>,
 PHP Internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <3A78AC53-5235-4CFE-9F0D-21F5837B6025@gmail.com>
References: <CD067B03-8DE2-42E4-9DA3-34C8B3D0B3D2@gmail.com> <E3.2B.14237.979C4E65@pb1.pair.com> <56F40965.30302@telia.com>
To: =?utf-8?Q?Bj=C3=B6rn_Larsson?= <bjorn.x.larsson@telia.com>
Subject: Re: [PHP-DEV] Re: [RFC Proposal] Null Coalesce Equal Operator
From: mtkocak@gmail.com (Midori Kocak)

there were no suggestions. Do you have one?

> On 24 Mar 2016, at 16:36, Bj=C3=B6rn Larsson =
<bjorn.x.larsson@telia.com> wrote:
>=20
> Den 2016-03-13 kl. 02:59, skrev Andrea Faulds:
>> Hi Midori,
>>=20
>> Midori Kocak wrote:
>>> Forgive my rookieness and let me introduce my first RFC here: =
https://wiki.php.net/rfc/null_coalesce_equal_operator =
<https://wiki.php.net/rfc/null_coalesce_equal_operator>
>>=20
>> I think this is a reasonable proposal. I had foreseen that we might =
add a ??=3D operator some day when I wrote the original RFC for the ?? =
operator.
>>=20
>> I do have one thing to add, though. It's something of a nitpick, but =
the name ought to be the "null-coalescing assignment operator". This =
would follow the convention of referring to +=3D, -=3D etc. as =
compound/combined assignment operators[1][2], not "equal" operators =
(which sounds more like what =3D=3D and =3D=3D=3D do, to me) and avoids =
the mistake ("coalesce" instead of "coalescing") that I originally made =
in my RFC for ??.[3] I think that RFC naming is important, because the =
name the author chooses for a feature tends to be the one that ends up =
in the manual.
>>=20
>> Anyway, thank you for your RFC!
>>=20
>> [1] http://php.net/manual/en/language.operators.assignment.php
>> [2] =
https://github.com/php/php-langspec/blob/master/spec/10-expressions.md#com=
pound-assignment
>> [3] https://blog.ajf.me/2015-12-07-poorly-named-rfcs
>=20
> Any conclusion on naming of operator, remain or change?
>=20
> Regards //Bj=C3=B6rn
>=20