Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:81767
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.41 as permitted sender)
Message-ID: <54D1BC7D.5000504@gmail.com>
Date: Tue, 03 Feb 2015 22:30:21 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Adam Harvey <aharvey@php.net>, Anatol Belski <anatol.php@belski.net>
CC: PHP internals <internals@lists.php.net>
References: <cef015a176ff63284f81af24f1e3d774.squirrel@webmail.klapt.com> <CADajX4DwhhPudqixn7Ck=LUKX9XH4mpdFgvADhF0tmXMPTYueQ@mail.gmail.com>
In-Reply-To: <CADajX4DwhhPudqixn7Ck=LUKX9XH4mpdFgvADhF0tmXMPTYueQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] [RFC][VOTE] Removal of dead or not yet PHP7 ported
 SAPIs and extensions
From: smalyshev@gmail.com (Stanislav Malyshev)

Hi!

I am kind of surprised that RFC about removing whole extensions has
"Backward Incompatible Changes" listed as "None". Really? No BC impact
whatsoever by removing imap and mcrypt? Literally nobody ever anywhere
is using it?

> - ext/imap and ext/mcrypt: while I realise that the underlying
> libraries are dead, these extensions are too widely used to straight
> up remove them, I fear — we don't have obvious alternatives with
> simple enough APIs that we can push users towards. I'd strongly
> support and encourage a reimplementation of these extensions (in C or
> PHP) around something supported if someone was able to step up and do
> the work, otherwise yes, I'll pitch in to do the minimal work to port
> these to 7.0 if required.

IIRC imap is working with PHP 7 and passes the tests on CI currently.
mcrypt seems to be enabled on CI too. So what is needed for them for 7.0?

-- 
Stas Malyshev
smalyshev@gmail.com