Re: Revisiting RFC: Engin e Warnings -- Undefined array index
| From: | Derick Rethans | Date: | Tue, 13 Dec 2022 22:51:44 +0000 |
| Subject: | Re: Revisiting RFC: Engin e Warnings -- Undefined array index | ||
| References: | 1 2 3 4 5 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-119140@lists.php.net to get a copy of this message | ||
On 13 December 2022 15:55:41 GMT, Thomas Hruska <thruska@cubiclesoft.com> wrote:
>On 12/13/2022 7:15 AM, Derick Rethans wrote:
>> On Mon, 12 Dec 2022, Thomas Hruska wrote:
>>
>>> On 12/12/2022 3:52 PM, Derick Rethans wrote:
>>>> On 12 December 2022 22:20:27 GMT, Dan Liebner <dliebner@gmail.com> wrote:
>>>>
>>>>> It has been proposed to make the error level of "Undefined index"
>>>>> configurable so that teams and individual developers can decide
>>>>> for themselves how they want this situation to be handled. Given
>>>>> that:
>>>>>
>>>>> - PHP has been treating this as an E_NOTICE for over 20 years
>>>>
>>>> But not in the last three years.
>>>
>> <snip>
>>
>>> The type of post that the OP sent to internals is likely to become
>>> more common in the next few months as PHP 8.x starts rolling out
>>> globally.
>>
>> PHP 8 has been rolling out for two years "globally" already.
>
>Not for those of us that run the package managed version of PHP in Ubuntu Server LTS it
>hasn't.
That's your and their choice, and not a problem that we here should care about. I certainly
don't.
There are also well established third party repositories (sury and remi) to cater for this use case
as well.
From the PHP project's point of view, PHP 8 has been out for more than two years.
cheers
Derick