Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:113965
To: internals@lists.php.net
References: <0b8301d72a3a$71045ca0$530d15e0$@webkr.de>
 <DC22B556-A023-4F10-BE20-79857C93A58A@benramsey.com>
 <55DEACD7-E0E8-45AD-84F2-A98D8AEEDC4D@newclarity.net>
 <0ba001d72a55$187ab280$49701780$@webkr.de>
Message-ID: <06b9663f-1495-1eb7-973f-bb24b062b393@gmail.com>
Date: Mon, 5 Apr 2021 21:10:09 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
 Thunderbird/78.9.0
MIME-Version: 1.0
In-Reply-To: <0ba001d72a55$187ab280$49701780$@webkr.de>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-GB
Subject: Re: [PHP-DEV] Raising the precedence of the new operator
From: rowan.collins@gmail.com (Rowan Tommins)

On 05/04/2021 20:51, André Hänsel wrote:
> Note that in that bug entry the solution was based on the premise that `$obj = new $foo->bar();` was valid code, which
> it isn't. (https://3v4l.org/lpN1T)


Looking at the error message, that code parsed as valid, but failed at 
run-time, because it was looking for a property $bar, not a method 
bar(). Working version: https://3v4l.org/S9gLf

It's equivalent to:

$className = $foo->bar;
$obj = new $className();


I think this means that just changing the operator precedence would be a 
compatibility break, and we would need to allow a more restricted 
version, as discussed on that feature request.

Regards,

-- 
Rowan Tommins
[IMSoP]