Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:63809
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain adamharvey.name designates 209.85.219.42 as permitted sender)
MIME-Version: 1.0
Sender: adam@adamharvey.name
In-Reply-To: <CAMUwpuQr7+nZoQpdRKGT+6GrM55Mv0g7_Aun2XW8GTGKQohqHQ@mail.gmail.com>
References: <CADajX4CYZdNpgQv46m_6J7tQLBc=h6HxCn-bGpxr3Ou2VaqgBg@mail.gmail.com>
 <50A0F797.30604@daylessday.org> <CAMUwpuQr7+nZoQpdRKGT+6GrM55Mv0g7_Aun2XW8GTGKQohqHQ@mail.gmail.com>
Date: Mon, 12 Nov 2012 22:17:13 +0800
Message-ID: <CADajX4DEFKzOuTVmzkvnSyO+843xCS5Vu0ihuDdyj9z9UBwMnQ@mail.gmail.com>
To: jpauli <jpauli@php.net>
Cc: internals@lists.php.net
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] RFC: ext/mysql deprecation
From: aharvey@php.net (Adam Harvey)

On 12 November 2012 22:01, jpauli <jpauli@php.net> wrote:
> 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 :)

I agree, but I feel as though we started this process last year.
(Informally, really, we'd been doing it for a while before that.)

It may or may not be too early to attach E_DEPRECATED to
mysql_connect() =E2=80=94 that's why I'm asking. Obviously, I think it's a
reasonable time, personally, but fortunately for everyone, I'm not the
arbiter of what goes into PHP.

Adam, who promises not to reply to any other e-mails until tomorrow.
Mostly because it's nearing on bedtime.