Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:63850
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.161.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAAyV7nFOGa7UVALSQyAs-A+R0kuEmXoHPrxvCXNBnzAxLy0dww@mail.gmail.com>
References: <CADajX4CYZdNpgQv46m_6J7tQLBc=h6HxCn-bGpxr3Ou2VaqgBg@mail.gmail.com>
 <50A10A9D.9070402@oracle.com> <CAAyV7nF2tt6HtFZKevH_2kknqOvEmLJjEOF2_Bn_VHaZFUJERw@mail.gmail.com>
 <CAPwsocH3_qHSZbLFe27qX+KgBAC1D8KhwLi+PLHW503sCTBtTw@mail.gmail.com>
 <50A1946F.8010407@lerdorf.com> <50A20CCB.8090909@lsces.co.uk>
 <8A8A29F9E43E417FB5450D63019B2DDB@NeiRoze> <8f4231fc-6e3c-4a33-af71-2af5e7a95dfd@email.android.com>
 <CAAyV7nFOGa7UVALSQyAs-A+R0kuEmXoHPrxvCXNBnzAxLy0dww@mail.gmail.com>
Date: Tue, 13 Nov 2012 18:41:28 +0000
Message-ID: <CAPg3XxJQoHGAeN_deAhY14cradmav7P4Fz85HEgXnfKO6o8U4g@mail.gmail.com>
To: Anthony Ferrara <ircmaxell@gmail.com>
Cc: =?ISO-8859-1?Q?Johannes_Schl=FCter?= <johannes@schlueters.de>, 
	Reinis Rozitis <r@roze.lv>, PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] RFC: ext/mysql deprecation
From: petercowburn@gmail.com (Peter Cowburn)

On 13 November 2012 16:07, Anthony Ferrara <ircmaxell@gmail.com> wrote:
> What I would suggest, is not adding E_DEPRECATED for 5.5. Instead,
> officially deprecate it in the docs. Then start a PR campaign to get
> projects like WP to switch away from it. Get the word out there as much as
> possible. Then in 1 to 2 years when 5.6/6 is released, add E_DEPRECATED.
>

A very brief interjection from the documentation team's side of the
fence (though I can't speak for everyone).  Extensions, functions,
etc. marked as deprecated in the documentation reflect the reality in
the code.  If a function is deprecated in php-src, then we document it
as such in the manual.  Since ext/mysql is not yet deprecated in the
source, we cannot "officially deprecate it in the docs" with the usual
"this function is deprecated, blah, blah" messages.  This is why we
have adopted the "soft-deprecation" boxes in the manual especially for
ext/mysql, to step forward with that PR campaign (which has been going
on for years upon years) until such a time as the extension is
actually marked as deprecated in php-src.

Long story short, the manual reflects the source.  Put the deprecation
into a release and we can document the extension as such. Hold back on
the deprecation in the source and we can't stick a paragraph in the
docs saying "this is deprecated", rather we can only continue to say
that its use is "discouraged".