Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:63806
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.170 as permitted sender)
MIME-Version: 1.0
Sender: julienpauli@gmail.com
In-Reply-To: <50A0F797.30604@daylessday.org>
References: <CADajX4CYZdNpgQv46m_6J7tQLBc=h6HxCn-bGpxr3Ou2VaqgBg@mail.gmail.com>
 <50A0F797.30604@daylessday.org>
Date: Mon, 12 Nov 2012 15:01:42 +0100
Message-ID: <CAMUwpuQr7+nZoQpdRKGT+6GrM55Mv0g7_Aun2XW8GTGKQohqHQ@mail.gmail.com>
To: Antony Dovgal <tony@daylessday.org>
Cc: internals@lists.php.net
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] RFC: ext/mysql deprecation
From: jpauli@php.net (jpauli)

On Mon, Nov 12, 2012 at 2:20 PM, Antony Dovgal <tony@daylessday.org> wrote:
> On 2012-11-12 17:00, Adam Harvey wrote:
>>
>> Hi everyone,
>>
>> I've written an RFC to cover deprecating ext/mysql in PHP 5.5:
>> https://wiki.php.net/rfc/mysql_deprecation. While we handled the soft
>> deprecation in the documentation purely via a straw poll on Internals,
>> I presume this will end up needing to go to a vote, hence the RFC.
>>
>> I won't rehash the background overly (there's some more detail in the
>> RFC), other than to note that we've now had deprecation notices on all
>> mysql_* functions in the manual for about six months and that the
>> logical next step is to start generating E_DEPRECATED notices when
>> users connect via mysql_connect(), mysql_pconnect() or the implicit
>> ext/mysql connection routines.
>
>
> While I fully understand the reasons behind this, I still believe this kind
> of thing should be done using the documentation only.
>
> Generating 'educational' notices will just annoy the end users and in 99%
> cases they can't do a thing about it -
> nobody's going to rewrite a large piece of legacy software just to make PHP
> happy.
>
> More notices doesn't necessarily mean less people are going to use
> ext/mysql,
> you can't hasten users to move if they don't really want to do it
> themselves.

Well, I think we can communicate, then educate people so that they
dont use ext/mysql any more.
It will take the time needed, but if we want this move to come up, we
need to start it. Doing nothing about it, things wont move.

I like educating through the documentation / through conferences, then
through the code, using the designed-for-that E_DEPRECATED , then
removing the extension.
It may take years, but such a project should be clear to everybody
(RFC), accepted, and started :)

Julien.Pauli