Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:120903
MIME-Version: 1.0
References: <CAFPFaMLBZixUFa=7=9Gxj60D=4QyfSpF9se-U+6CRoShzCrFrA@mail.gmail.com>
 <8a9b7bc7-5d3d-46a3-bf3c-0af66aa2796f@app.fastmail.com>
In-Reply-To: <8a9b7bc7-5d3d-46a3-bf3c-0af66aa2796f@app.fastmail.com>
Date: Mon, 14 Aug 2023 21:14:40 +0100
Message-ID: <CAFPFaMJLn1ont4vifoNTxR05LcJRVLMe_ccO5P3hEpKLe_hYzQ@mail.gmail.com>
To: Larry Garfield <larry@garfieldtech.com>
Cc: php internals <internals@lists.php.net>, Jakub Zelenka <bukka@php.net>, eric@eamann.com, 
	adoy@php.net
Content-Type: multipart/alternative; boundary="0000000000000e19e10602e7b770"
Subject: Re: [PHP-DEV] Removing support for the disable_classes INI setting
From: george.banyard@gmail.com ("G. P. B.")

--0000000000000e19e10602e7b770
Content-Type: text/plain; charset="UTF-8"

On Mon, 14 Aug 2023 at 20:03, Larry Garfield <larry@garfieldtech.com> wrote:

> However, I think it should not get an exception for code-freeze.  At best,
> I could see a deprecation warning on it in 8.3 and remove in 8.4/9, but I
> defer to the RMs on that front.
>

In its current state, this INI setting does nothing other than cause
segfaults.
This functionality is broken, and frankly has always been.
The only reason I am asking for an exception is to remove broken
functionality that doesn't work and cannot be easily fixed.

George P. Banyard

--0000000000000e19e10602e7b770--