Re: [RFC] [VOTE] Cleaning up unmaintained extensions
| From: | Yasuo Ohgaki | Date: | Sat, 30 Jun 2018 01:44:16 +0000 |
| Subject: | Re: [RFC] [VOTE] Cleaning up unmaintained extensions | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-102533@lists.php.net to get a copy of this message | ||
On Fri, Jun 29, 2018 at 2:16 PM, Tim Starling <tstarling@wikimedia.org>
wrote:
> On 20/06/18 05:46, Stanislav Malyshev wrote:
> > Hi!
> >
> >> Hi!
> >>
> >> I would like to open the vote for the RFC about cleaning up the
> >> unmaintained extensions:
> >>
> >> https://wiki.php.net/rfc/umaintained_extensions
> >>
> >> <https://wiki.php.net/rfc/umaintained_extensions>
> >>
> >> The vote ends 2018-06-26 23:59 PDT.
> >>
> >>
> >> Just to be sure consequence of "readline" removal.
> >>
> >> With CLI, "php -a" and "history" works without readline?
> >> Does it work as dynamically loaded module?
> >
> > CLI can still use readline library. This would be about readline PHP
> > extension.
> >
>
> Actually, readline support in "php -a" is part of the extension. The
> extension hooks the SAPI module. See PHP_MINIT_FUNCTION(cli_readline)
> in readline_cli.c.
>
> Readline is the only extension in your list that I would be sad about
> losing. I use it every day, I guess a lot of devs do.
>
readline has license issue. I miss it but I wouldn't object for removing it.
Let's use libedit for CLI by default and always.
Issue may be who is going to do this. If nobody volunteers, I may do this.
--
Yasuo Ohgaki