Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:74806
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.182 as permitted sender)
MIME-Version: 1.0
Sender: rdlowrey@gmail.com
Date: Mon, 9 Jun 2014 12:53:24 -0400
Message-ID: <CAH8MpnmwUNnO4vgVJ+yx9NcdWboYxMMUUf0bKxY4PHQEpTK-qQ@mail.gmail.com>
To: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=047d7bdc193aaf64cf04fb6a0ccf
Subject: Re: Uniform Variable Syntax
From: rdlowrey@php.net (Daniel Lowrey)

--047d7bdc193aaf64cf04fb6a0ccf
Content-Type: text/plain; charset=UTF-8

On 9 June 2014 06:33, Nikita Popov <nikita.ppv@gmail.com> wrote:
> I have created a proposal for a more consistent and complete variable
> syntax for PHP 6:
>
>     https://wiki.php.net/rfc/uniform_variable_syntax
>
> The RFC is targeted at PHP 6 because it breaks compatibility for some
> rarely used variable-variable constructs.

At the risk of saying, "me too, me too!" I want to pass along my
support for this RFC. Uniformity and consistency are worthwhile goals;
the fewer special cases that exist the fewer things I have to keep in
my small brain at once. In particular, this is something I've seen
several userland devs ask for ($func()()) and of which I've found
myself desirous.
Further, this set of changes will likely not -- unlike the
oft-proposed "parameter order consistency" faux improvements -- break
BC all over the place.
Thanks for the work, Nikita.


-Daniel

--047d7bdc193aaf64cf04fb6a0ccf--