Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:63980
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAFMT4No1Fr5gL4t8=NcUtzY8nW-=_=+sLEja9kuWt4MT_DKnmQ@mail.gmail.com>
References: <CADajX4CYZdNpgQv46m_6J7tQLBc=h6HxCn-bGpxr3Ou2VaqgBg@mail.gmail.com>
	<CACwt+JeLin8aLtmBedO+DnJ4cz0Ajb75depkd7v_QK1NORUPOg@mail.gmail.com>
	<CADajX4CmOEBy3aZOh+qpfmq=OTiLF6+EuOyiRWM2bx7JxZumrg@mail.gmail.com>
	<50A9F799.5080909@codeangel.org>
	<CADajX4CbLLagJnO+dkZsGXkaS8h7rabtmpOz6Gos0KqcHOpsMA@mail.gmail.com>
	<CAAyV7nF3VyvCa_YCYrtaajm8b8CpTCUq7M6=07hJ5eCGBaUZrA@mail.gmail.com>
	<CAEZPtU6DG049yezXJtUrbbVQnWVwZpnsANhQG9ZsZzESBb1-Mg@mail.gmail.com>
	<CAAyV7nH3in_s8f_NAupb_HWy5ZQuCrf8qw+Ah7A2v0sap+3GTQ@mail.gmail.com>
	<CAKOpQSyGJLtX9=+9nvQANWWUBAAkTu3wwbX=cFOarLYyyQ6kMQ@mail.gmail.com>
	<CAAyV7nHvTNoz1KxrwZXAy02GeLMf=9W3Kmx+r0GY48AcVmU7Mw@mail.gmail.com>
	<CAFMT4No1Fr5gL4t8=NcUtzY8nW-=_=+sLEja9kuWt4MT_DKnmQ@mail.gmail.com>
Date: Mon, 19 Nov 2012 10:29:11 -0800
Message-ID: <CAKOpQSynKQ7tmxku-6bzPBN+D7Nd_xd4OKg-nxPqum9upUyybg@mail.gmail.com>
To: Levi Morrison <morrison.levi@gmail.com>
Cc: Anthony Ferrara <ircmaxell@gmail.com>, Pierre Joye <pierre.php@gmail.com>, 
	Adam Harvey <aharvey@php.net>, Chad Emrys <admin@codeangel.org>, 
	Patrick Allaert <patrickallaert@php.net>, 
	"internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=f46d040714af3abdfc04cedd4b83
Subject: Re: [PHP-DEV] RFC: ext/mysql deprecation
From: kris.craig@gmail.com (Kris Craig)

--f46d040714af3abdfc04cedd4b83
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Nov 19, 2012 at 9:49 AM, Levi Morrison <morrison.levi@gmail.com>wrote:

> On Mon, Nov 19, 2012 at 10:22 AM, Anthony Ferrara <ircmaxell@gmail.com>
> wrote:
> > And in either case, removal would happen one release after hard
> > deprecation.
>
> I'd actually propose that it is removed in PHP 6, even if there is PHP
> 5.6 and 5.7, etc. Something can be deprecated for several versions.
> It is a significant change that seems more suited to a major release
> such as 6.0.0.
>
> This is slightly off-topic since this is about when we deprecate, not
> when we remove.
>

I think they kinda go hand-in-hand though.  And yes I agree; 6.0 should be
the target for removal.  In fact, I'm of the opinion that *everything* that
was hard-deprecated in 5.x should be removed completely in 6.0.  People
understand that some BC will occur in major version increments.  Adoption
would and should be a gradual process for that reason as people update
their code to the latest standards.  It also gives us the freedom to make
more fundamental improvements to the language if deemed necessary.

--Kris

--f46d040714af3abdfc04cedd4b83--