Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:117050 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 68805 invoked from network); 17 Feb 2022 07:23:08 -0000 Received: from unknown (HELO localhost.localdomain) (76.75.200.58) by pb1.pair.com with SMTP; 17 Feb 2022 07:23:08 -0000 To: internals@lists.php.net Date: Thu, 17 Feb 2022 08:41:18 +0000 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.6.0 References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Posted-By: 87.81.129.66 Subject: Re: Setting to disable the "Undefined array index" warning From: marandall@php.net (Mark Randall) Message-ID: On 15/02/2022 12:31, Nicolas BADIA wrote: > As I’m not ready to spend weeks upgrading our codebase because our coding style is not supported by the community, I’m looking at alternatives. I don't think you'll be in luck, and should plan to get ready. As to the specific behaviour: If anything this behaviour will get tighter over time, and it's entirely possible that in a later major release it will throw an error (although that's not being proposed right now). From my conversations, there is little apetite to add additional INI based controls for engine behaviour, as they are believed to lead to inconsistencies that harm the ecosystem, rather than enhance it. Forking PHP to avoid resolving ambiguities in your code seems like it would be a false economy. Ideally you should bring your code up-to-date with what is expected, but if you are unwilling or unable to do that, you may instead wish to stay on an older version that hax more lax behaviour, and purchase LTS from the likes of Zend. Mark Randall