Re: Setting to disable the "Undefined array index" warning

From: Date: Thu, 17 Feb 2022 08:41:18 +0000
Subject: Re: Setting to disable the "Undefined array index" warning
References: 1  Groups: php.internals 
Request: Send a blank email to internals+get-117050@lists.php.net to get a copy of this message
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

« previous php.internals (#117050) next »