Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:74814
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.174 as permitted sender)
Message-ID: <5396EE23.7040909@gmail.com>
Date: Tue, 10 Jun 2014 12:38:11 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: internals@lists.php.net
References: <CAF+90c-jyBCnHdYjssGV+Avsw2B=Zt8TpNUzuDsNDWabV43fQg@mail.gmail.com> <5395CC8D.5060702@anderiasch.de> <5395DB90.40307@gmail.com>
In-Reply-To: <5395DB90.40307@gmail.com>
Content-Type: multipart/alternative;
 boundary="------------020202030403080900060407"
Subject: Re: [PHP-DEV] [RFC] [PHP 6] Uniform Variable Syntax
From: rowan.collins@gmail.com (Rowan Collins)

--------------020202030403080900060407
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Rowan Collins wrote (on 09/06/2014):
> The advantage of the proposed behaviour is that it can be easily 
> explained to *new* users of the language, as it's internally 
> consistent, which appears not to be true of the old - an example in 
> the RFC being |Foo::$bar[1][2][3] vs ||Foo::$bar[1][2][3]()| 

A simpler example of the current logic's inconsistencies:

$foo = 'foo';
$bar->$foo = array();
$bar->$foo[0] = 42;
// $bar now has an array on ->foo, and an integer on ->f

http://3v4l.org/pImS3

Not only does this not feel consistent in itself, it's different if you 
do the same thing with an object:

$foo = 'foo';
$bar->$foo = new stdClass;
$bar->$foo->x = 42;
// $bar now has a single property ->foo, which is an object with 
property ->x

http://3v4l.org/DUaJj

Other than "it's always worked this way", I can't think of a good 
justification for this difference.

-- 
Rowan Collins
[IMSoP]

--------------020202030403080900060407--