Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:63814
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.54 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <50A10A9D.9070402@oracle.com>
References: <CADajX4CYZdNpgQv46m_6J7tQLBc=h6HxCn-bGpxr3Ou2VaqgBg@mail.gmail.com>
	<50A10A9D.9070402@oracle.com>
Date: Mon, 12 Nov 2012 09:50:37 -0500
Message-ID: <CAAyV7nF2tt6HtFZKevH_2kknqOvEmLJjEOF2_Bn_VHaZFUJERw@mail.gmail.com>
To: Ulf Wendel <ulf.wendel@oracle.com>
Cc: Adam Harvey <aharvey@php.net>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=f46d044289c4a677b804ce4d6c81
Subject: Re: [PHP-DEV] RFC: ext/mysql deprecation
From: ircmaxell@gmail.com (Anthony Ferrara)

--f46d044289c4a677b804ce4d6c81
Content-Type: text/plain; charset=ISO-8859-1

My standpoint would be not to add E_DEPRECATED notices in 5.5... It's
simply used too much to start loudly complaining about it. Instead, what I
would suggest is the following:

1. Officially deprecate it now. Right now, on the docs it says
"discouraged", but I would suggest changing that to officially deprecated.
2. The next release (5.6 or 6) would add deprecation errors to the code.
3. The next release (5.7 or 6 or 6.1, etc) would then remove the extension
entirely.

That way there's a significant roadmap towards deprecation, and people can
migrate their code in tune. Sure, there are people who won't do anything
and will break on that major release, but there's not much we can do about
that anyway...

Just my $0.02...

--f46d044289c4a677b804ce4d6c81--