Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:111162
Message-ID: <tencent_3FD771EC4A53CD30B9F99C1B2F17EDE7CE06@qq.com>
Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
In-Reply-To: <CAF+90c82geReCwnejGM0Lg9UYyEoD6AyBYt+E7hj=x5aTmXK9w@mail.gmail.com>
Date: Fri, 24 Jul 2020 19:39:03 +0800
Cc: PHP internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
References: <CAF+90c82geReCwnejGM0Lg9UYyEoD6AyBYt+E7hj=x5aTmXK9w@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Subject: Re: [PHP-DEV] Ternary associativity
From: twose@qq.com (twosee)


> 2020=E5=B9=B47=E6=9C=8823=E6=97=A5 =E4=B8=8B=E5=8D=888:26=EF=BC=8CNikita=
 Popov <nikita.ppv@gmail.com> =E5=86=99=E9=81=93=EF=BC=9A
>=20
> Hi internals,
>=20
> PHP currently has an incorrect right-associative ternary operator. In
> https://wiki.php.net/rfc/ternary_associativity the use of nested =
ternaries
> was deprecated, and was supposed to become an error in PHP 8.0.
>=20
> Concurrently with that proposal
> https://wiki.php.net/rfc/concatenation_precedence made a very similar
> change to the concatenation operator precedence. The difference here =
is
> that this throws a deprecation notice in PHP 7.4 (same), but changes =
the
> behavior in PHP 8.0 (rather than making it an error).
>=20
> This is a pretty nonsensical outcome, in that the same type of change =
is
> implemented in two different ways. I think it would be good to handle =
the
> ternary change the same way as the concatenation change, i.e. make
> ternaries use the correct left-associative behavior in PHP 8.0, rather =
than
> throwing an error.
>=20
> Any thoughts on that?
>=20
> Regards,
> Nikita

I would rather both of them become errors
It is evil to use associativity instead of explicit parentheses
The evaluation results of these two RFCs are that the impact of these =
changes should be minimal and it almost always is an error, so if we =
want to make them consistent, why not make them all become errors?

Regards,
Twosee