Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:82471
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.171 as permitted sender)
Message-ID: <54DB3EE6.6070104@gmail.com>
Date: Wed, 11 Feb 2015 11:37:10 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: internals@lists.php.net
References: <bc6d032454578020cdd2cef172698534.squirrel@webmail.klapt.com> <54DB3184.8080408@seld.be>
In-Reply-To: <54DB3184.8080408@seld.be>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC][VOTE][RESULT] Removal of dead or not yet PHP7
 ported SAPIs and extensions
From: rowan.collins@gmail.com (Rowan Collins)

Jordi Boggiano wrote on 11/02/2015 10:40:
> On 09/02/2015 22:29, Anatol Belski wrote:
>> ext/imap
>> ext/mcrypt
>> ext/pdo_dblib
>
> Sorry if this was suggested already but if those are not maintained 
> much and should not be used further ideally, shouldn't we add 
> E_DEPRECATED to them at least?
>
> I understand that they are kept to avoid making the upgrade path 
> harsher, but it's also not great to let they linger on forever with no 
> notice to users that they are doing something wrong.

I guess that's a discussion that can be had on a case-by-case basis, now 
we've bulk-voted the easy cases out of the way.

Deprecation only really makes sense if there is a clear upgrade path for 
users, or a specific message to give them. For instance, I'm currently 
using PDO_DBLIB, and had no idea I was "doing something wrong", or what 
I should be doing instead. And many people have already pointed out that 
ext/mcrypt needs some special thought, so just slapping a deprecation 
notice somewhere isn't really that useful.

Regards,
-- 
Rowan Collins
[IMSoP]