Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:102302
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain schlueters.de from 84.19.169.162 cause and error)
Message-ID: <1529411849.2713.46.camel@schlueters.de>
To: "Christoph M. Becker" <cmbecker69@gmx.de>, Stanislav Malyshev
	 <smalyshev@gmail.com>, PHP Internals <internals@lists.php.net>
Date: Tue, 19 Jun 2018 14:37:29 +0200
In-Reply-To: <eedcc507-53ce-257e-d2d5-1365c5228b42@gmx.de>
References: <f790ef52-0a92-a8a3-bb3d-891713b390be@gmail.com>
	 <eedcc507-53ce-257e-d2d5-1365c5228b42@gmx.de>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] Re: [RFC] orphan extensions cleanup
From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=)

Hi,

On Di, 2018-06-12 at 13:54 +0200, Christoph M. Becker wrote:

> > https://wiki.php.net/rfc/umaintained_extensions
> 
> I think it is *very* important to finally tackle this topic.  Since
> it


It's a good subject to think about, but we should be careful not to end
with a process and then following it without thought and we have to
look at those things individually.

For instance with readline this contains two things. For one the
`readline()` and related userspace functions, which I assume are not
used thaaaat often, but also the interactive shell mode (`php -a` with
CLI+readline enabled) and I think the later is quie important to many
users and should see similar common responsibility as those key SAPIs,
main/ and so on. (I once moved that functionality from SAPI/cli to
ext/readline to satisfy distributors who didn't want to statically link
readline for license and related reasons)

johannes