Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:117345 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 38478 invoked from network); 16 Mar 2022 07:35:48 -0000 Received: from unknown (HELO localhost.localdomain) (76.75.200.58) by pb1.pair.com with SMTP; 16 Mar 2022 07:35:48 -0000 To: internals@lists.php.net Date: Wed, 16 Mar 2022 09:00:44 +0000 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 References: <4724184.31r3eYUQgx@come-prox15amd> <37421f61-4e2e-53d3-56d0-022a3c21ed2e@gmx.de> <4f8bad56-267a-9279-1e57-66fd10b8874f@gmail.com> <6230f8bf.1c69fb81.b1e54.162dSMTPIN_ADDED_MISSING@mx.google.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Posted-By: 149.241.136.89 Subject: Re: [PHP-DEV] [VOTE] Undefined Variable Error Promotion From: marandall@php.net (Mark Randall) Message-ID: On 15/03/2022 23:02, Patrick ALLAERT wrote: > I am not against the fact this warning becomes an error per se. I am just > not very fan of cherry-picking an individual kind of problem (read: > notice/warning/error/...) and changing it without a more global frame. I think we should try to hit all of them, ideally in time for PHP 9. That was the premise behind: https://externals.io/message/116918 It will likely take several RFCs until we've got it in the state we want it, some of those are more contentious than others (such as undefined array indexes). I think undefined property access should throw too, and will likely have supermajority support, but let's do it in a separate RFC. What I don't think we want is the entire package being blocked because a particular item (i.e. array keys) is contentious.