Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:107602
To: David Negrier <d.negrier@thecodingmachine.com>, internals@lists.php.net
References: <CAJkq-zzRaVYVvQ_pJbKu1vGNTQSTZ_pFF6yzhVrDF4N-M8NbiA@mail.gmail.com>
Message-ID: <5749da37-2c50-b32f-47a3-c2ff4e3aab65@xs4all.nl>
Date: Mon, 21 Oct 2019 17:17:29 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <CAJkq-zzRaVYVvQ_pJbKu1vGNTQSTZ_pFF6yzhVrDF4N-M8NbiA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Reclassifying some PHP functions warning as exceptions
From: d.takken@xs4all.nl (Dik Takken)

On 21-10-19 11:10, David Negrier wrote:
> I'm considering writing an RFC (and a patch) to turn some warning into
> exceptions in a number of PHP functions.
> I would first like to gather some feedback here.

I think this is definitely worth a shot. My suggestion would be to split
the effort in sets of functions based on the amount of BC break that
would be involved.

Functions that would require a minor BC break that is unlikely to affect
a lot of code could be bundled in one RFC. The list of functions could
then be discussed and finally voted on. Another RFC could address
functions that are expected to cause bigger BC issues which could be
fixed using an automatic fixer. Yet another RFC for functions that would
require manual fixing of BC issues. Some of these functions might
require an RFC of their own. A step at a time.

Regards,
Dik Takken