Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:117113 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 83023 invoked from network); 22 Feb 2022 09:48:20 -0000 Received: from unknown (HELO localhost.localdomain) (76.75.200.58) by pb1.pair.com with SMTP; 22 Feb 2022 09:48:20 -0000 To: internals@lists.php.net Date: Tue, 22 Feb 2022 11:07:46 +0000 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.6.1 References: <620eda0f.1c69fb81.d2cb1.0846SMTPIN_ADDED_MISSING@mx.google.com> <5efecaef-a024-3c61-e12e-ffc342956718@gmail.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Posted-By: 87.81.129.66 Subject: Re: [PHP-DEV] [RFC] Undefined Variable Error Promotion From: marandall@php.net (Mark Randall) Message-ID: On 22/02/2022 09:15, Nicolas Grekas wrote: > I very much call for an implementation to be provided before starting any > vote on the topic btw. The RFC states on its first line that accessing an undefined variable emits an E_WARNING. If it does not currently emit an E_WARNING then it is out of scope of this RFC. It is not sensible to provide a full implementation for something that will require extensive engine and test changes for something several years into the future, during which many other changes will be made. A sensible time for this would be after the branch is cut for 8.4.