Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:75315
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain ajf.me designates 192.64.116.199 as permitted sender)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
In-Reply-To: <CABBJUpcPO6fnmtCYjuD1iPqJdfn77R74Uie49Hr65WksY=mu+Q@mail.gmail.com>
Date: Mon, 7 Jul 2014 15:46:30 +0100
Cc: Nikita Popov <nikita.ppv@gmail.com>,
 PHP internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <4BB5E7E4-BCED-4271-BECC-804A1EDD4E53@ajf.me>
References: <CAF+90c9Fb0dswXcen8tnkQLEWhBymJ-w30z+p=vj3uRzdS3mGQ@mail.gmail.com> <CABBJUpcPO6fnmtCYjuD1iPqJdfn77R74Uie49Hr65WksY=mu+Q@mail.gmail.com>
To: Laruence <laruence@php.net>
Subject: Re: [PHP-DEV] [VOTE] Uniform Variable Syntax
From: ajf@ajf.me (Andrea Faulds)


On 7 Jul 2014, at 15:42, Laruence <laruence@php.net> wrote:

> 1. "The current patch introduces a new =93write context=94 issue. =
Namely
> ($foo)['bar'] =3D 'baz' will not behave this same was as $foo['bar'] =3D=

> 'baz'. In the former case an undefined variable notice will be thrown
> if $foo does not exist, whereas the latter does not throw a notice."
>=20
> 2. "As these changes only apply to some very rarely used syntax, the
> breakage seems acceptable for PHP 6."
>=20
>=20
> I don't think we should introduce a new thing which is not perfect or
> "confused".. it looks like we fixed a mess with a new mess.
>=20
> it make me think we should : "don't fix it until it is broken=94

We are fixing what is broken here; the variable syntax is =
counter-intuitive at the moment, and they make the syntax more =
consistent overall.

Also, parentheses in PHP are always a source of issues. I don=92t think =
they=92ll ever quite work properly unless we switch to using an =
AST-based parser someday.
--
Andrea Faulds
http://ajf.me/