Re: [RFC] Remove deprecated functionality in PHP 7
| From: | Rasmus Lerdorf | Date: | Sun, 12 Oct 2014 00:13:20 +0000 |
| Subject: | Re: [RFC] Remove deprecated functionality in PHP 7 | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-77886@lists.php.net to get a copy of this message | ||
> On Oct 11, 2014, at 16:47, Kris Craig <kris.craig@gmail.com> wrote:
>
>> On Oct 11, 2014 1:52 PM, "Nikita Popov" <nikita.ppv@gmail.com> wrote:
>>
>> Hi internals!
>>
>> We currently have a number of deprecated features, which we likely want to
>> remove in PHP 7. I've created a tracking RFC listing deprecated
>> functionality (if I missed something, please tell):
>>
>>
>> https://wiki.php.net/rfc/remove_deprecated_functionality_in_php7
>>
>> I expect many of these are no-brainers (like assigning new by-reference),
>> but other items like removal of ext/mysql may need additional
> consideration.
>>
>> Unless there are items that are particularly contested, I'd like to handle
>> the bulk of these in a single vote and only have separate votes for
>> ext/ereg and ext/mysql, as these are arguably more intrusive.
>>
>> Thanks,
>> Nikita
>
> +1 on all of that.
>
> As far as ext/mysql is concerned, I would eagerly vote in favor of removing
> it. It performs poorly, is procedural, less secure, doesn't support
> prepared statements, etc.
>
> It's always annoyed me how sites like w3schools still teach people to use
> ext/mysql. It's been deprecated for quite awhile now and I think it's time
> to pull the plug on it.
Keep in mind though that it would be mostly symbolic. The majority of users get their PHP and
extensions from distros. And distros have been separating out core-bundled extensions for a decade
now. Users have absolutely no idea whether their php-mysql package comes from core or from pecl, nor
do they care. So, unbundling it on our side will have close to zero impact on its use. In fact, in a
weird way it might actually help make people continue to use it because if we unbundle it and stick
it in pecl we would obviously not have it spew out 'deprecated' notices like we do as of
5.5. I mean, we still could, of course, but it would be weird having a non-core pecl extension
declare itself deprecated.
I am not against unbundling it, I just don't think it will achieve what you hope it will.
-Rasmus