Req #81417 [Opn]: Option to determine if reading an undefined array key should throw a warning

Edit report at https://bugs.php.net/bug.php?id=81417&edit=1 ID: 81417 User updated by: nicolas at gestixi dot com Reported by: nicolas at gestixi dot com -Summary: Add a configuration option to determine if reading an undefined array key shoul +Summary: Option to determine if reading an undefined array key should throw a warning Status: Open Type: Feature/Change Request Package: *Configuration Issues PHP Version: 8.0.10 Block user comment: N Private report: N New Comment: Adjust the summary which was too long. Previous Comments: ------------------------------------------------------------------------ [2021-09-05 12:20:50] nicolas at gestixi dot com Description: ------------ In some languages, such as JavaScript, accessing an undefined array key can be performed silently without throwing an error. We have a 10 years old code base which does conditions like this everywhere: if ($array['key']). With PHP 8, this coding style throws a warning if the key is not defined. Replacing it by if (array_key_exists('key', $array) && $array['key']) would take us weeks... and, I actually prefer our actual syntax which I found more readable. For these reasons, I do not plan to upgrade all our code base to avoid this warning. And I do not want to ignore all warnings just for this one... Would it be possible to add a configuration setting to determine if this coding style should throw a warning, a notice or be silently ignored? Another solution I see would be to be able to ignore specific warnings/notices. ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=81417&edit=1