Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:119110
Date: Mon, 12 Dec 2022 22:52:56 +0000
To: internals@lists.php.net, Dan Liebner <dliebner@gmail.com>
User-Agent: K-9 Mail for Android
In-Reply-To: <CAMXcktOiFH-0f0PG9cKkkVaczjNLSzQzzPUBcoLyn54X=c74og@mail.gmail.com>
References: <CAMXcktOiFH-0f0PG9cKkkVaczjNLSzQzzPUBcoLyn54X=c74og@mail.gmail.com>
Message-ID: <D494A14E-0733-406B-844E-DD2D3FBB7EB4@php.net>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: =?US-ASCII?Q?Re=3A_=5BPHP-DEV=5D_Revisiting_RFC=3A_Engin?= =?US-ASCII?Q?e_Warnings_--_Undefined_array_index?=
From: derick@php.net (Derick Rethans)

On 12 December 2022 22:20:27 GMT, Dan Liebner <dliebner@gmail=2Ecom> 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=2E Given that:
>
>   - PHP has been treating this as an E_NOTICE for over 20 years

But not in the last three years=2E=20

>   - the change is a breaking change affecting many large codebases
>   ubiquitously (unless one were to unadvisedly suppress E_WARNING errors=
)

No, code doesn't break=2E It now shows a warning instead of an error=2E Th=
ere is no behavioural change=2E=20

>   - 7=2E4 is now deprecated

Yes, as each release does 2+1 years=2E Which also means you've had 3 years=
 to address this in your code base(s) already=2E=20

>I think making the error level of "Undefined index" configurable is a ver=
y
>reasonable suggestion, and I support it=2E

Adding a configuration setting to make this a notice on some installations=
 and not on others, would just mean that anything that needs to be able to =
run everywhere needs to take care to not rely on the setting either way, ma=
king it harder to develop portable code=2E=20

We're also not generally anything near keen on adding settings that change=
 behaviour , and suggesting to add one to make a warning a notice seems ver=
y far short of a bar that needs to be reached before many of us would agree=
 to add a setting to make PHP less portable=2E=20

Alternatively you can just fix your code=2E=20

>Are we able to revisit this topic as a community and potentially bring in
>more PHP developers from around the world to weigh in?

You're always free to follow the RFC process, but I think you'll just up w=
asting your, and everybody else's, time with it=2E=20

I can't see this being reversed, nor a setting added for, through an RFC p=
rocess=2E=20

cheers=20
Derick=20