Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:77886
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lerdorf.com from 209.85.220.45 cause and error)
Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (1.0)
In-Reply-To: <CAKOpQSwgpU+T+W_5q+uftWzhtH8mvrqhidRArdfKP9fCYE1W5A@mail.gmail.com>
Date: Sat, 11 Oct 2014 17:13:20 -0700
Cc: Nikita Popov <nikita.ppv@gmail.com>,
 PHP internals list <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <3832FC29-CE4E-49C8-B9F1-3797F019D9F8@lerdorf.com>
References: <CAF+90c-B74M82xOkT1VguqShE3b2W2YLJ1HX_XzCJtG_WUSxxg@mail.gmail.com> <CAKOpQSwgpU+T+W_5q+uftWzhtH8mvrqhidRArdfKP9fCYE1W5A@mail.gmail.com>
To: Kris Craig <kris.craig@gmail.com>
Subject: Re: [PHP-DEV] [RFC] Remove deprecated functionality in PHP 7
From: rasmus@lerdorf.com (Rasmus Lerdorf)

> On Oct 11, 2014, at 16:47, Kris Craig <kris.craig@gmail.com> wrote:
>=20
>> On Oct 11, 2014 1:52 PM, "Nikita Popov" <nikita.ppv@gmail.com> wrote:
>>=20
>> Hi internals!
>>=20
>> We currently have a number of deprecated features, which we likely want t=
o
>> remove in PHP 7. I've created a tracking RFC listing deprecated
>> functionality (if I missed something, please tell):
>>=20
>>    https://wiki.php.net/rfc/remove_deprecated_functionality_in_php7
>>=20
>> 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.
>>=20
>> Unless there are items that are particularly contested, I'd like to handl=
e
>> 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.
>>=20
>> Thanks,
>> Nikita
>=20
> +1 on all of that.
>=20
> As far as ext/mysql is concerned, I would eagerly vote in favor of removin=
g
> it.  It performs poorly, is procedural, less secure, doesn't support
> prepared statements, etc.
>=20
> 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 tim=
e
> to pull the plug on it.

Keep in mind though that it would be mostly symbolic. The majority of users g=
et their PHP and extensions from distros. And distros have been separating o=
ut core-bundled extensions for a decade now. Users have absolutely no idea w=
hether their php-mysql package comes from core or from pecl, nor do they car=
e. So, unbundling it on our side will have close to zero impact on its use. I=
n 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 i=
t 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 i=
tself deprecated.=20

I am not against unbundling it, I just don't think it will achieve what you h=
ope it will.

-Rasmus=