Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:117463
Message-ID: <2f767271-5e57-2c29-bab5-1ad12bbcc8e9@gmail.com>
Date: Wed, 30 Mar 2022 19:58:56 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
 Thunderbird/91.7.0
Content-Language: en-GB
To: PHP Internals <internals@lists.php.net>
References: <9ecce8c9-c8bc-93e3-25f0-386c2c41ca1a@gmail.com>
 <CAC5V6ghWoAnqdp=vEuFAg-Wyg_Ydn5pAmVYDXqwsci+Xe9NnLw@mail.gmail.com>
In-Reply-To: <CAC5V6ghWoAnqdp=vEuFAg-Wyg_Ydn5pAmVYDXqwsci+Xe9NnLw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Undefined variables and the array append operator
From: rowan.collins@gmail.com (Rowan Tommins)

On 30/03/2022 15:32, Guilliam Xavier wrote:
> On the other hand, I agree that `$undefined[] = $x` looks like a 
> bug... are both cases the exact same opcode?


Some very good points raised in this thread about how many different 
closely-related cases there are here. I shall have to think clearly 
about which cases we want to change, and look at the implementation to 
see how easily those can be separated out from the others.

It sounds like there are at least some cases that might pass an RFC vote 
to change, though.

Regards,

-- 
Rowan Tommins
[IMSoP]