Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:63927
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain mybrokenlogic.com designates 216.86.156.70 as permitted sender)
Message-ID: <50A6314D.3060900@mybrokenlogic.com>
Date: Fri, 16 Nov 2012 12:27:57 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Rasmus Lerdorf <rasmus@lerdorf.com>
CC: Patrick ALLAERT <patrickallaert@php.net>, 
 Pierre Joye <pierre.php@gmail.com>,
 Anthony Ferrara <ircmaxell@gmail.com>, Will Fitch <willfitch@php.net>, 
 Stas Malyshev <smalyshev@sugarcrm.com>,
 Adam Harvey <aharvey@php.net>, Devis Lucato <devis@lucato.it>, 
 PHP Developers Mailing List <internals@lists.php.net>
References: <CADajX4CYZdNpgQv46m_6J7tQLBc=h6HxCn-bGpxr3Ou2VaqgBg@mail.gmail.com> <50A20CCB.8090909@lsces.co.uk> <8A8A29F9E43E417FB5450D63019B2DDB@NeiRoze> <8f4231fc-6e3c-4a33-af71-2af5e7a95dfd@email.android.com> <CAAyV7nFOGa7UVALSQyAs-A+R0kuEmXoHPrxvCXNBnzAxLy0dww@mail.gmail.com> <50A2D672.7010600@gmail.com> <50A30144.5070305@phpgangsta.de> <50A3BEC0.8030607@gmail.com> <CAET_qdMmhRyidM6_VOokBu6tYvgrPHMOPdzz0PaFpxc3NaTdYQ@mail.gmail.com> <CADajX4Bh+5YrCPEFLzC2qqeJ4NnADbBV0u+wByz3Kb7Jp45KOw@mail.gmail.com> <50A54713.8090102@sugarcrm.com> <CAArmra2bjj3y2UUV8nszU74tN9o4VvB67aXzq5Z1cE2Y_tVijg@mail.gmail.com> <50A549EB.2020408@lerdorf.com> <CAArmra2BCmbOjkK0D8gKc5o0Pwhx0jNGi-3m2C2Z2dAnb0yv7w@mail.gmail.com> <CAAyV7nGMi20xjBYbouvsyUrxdOSuboP6u-guY9DX8qkSagQbjg@mail.gmail.com> <CAEZPtU6mbLnaqijx3T942pULm-Y6a-4LPyk-H-WJ94NckkKbfw@mail.gmail.com> <50A5FB0C.1080602@lerdorf.com> <CACwt+Jdo6WO+VtYp6zSVM+a1GVGQHPxtPT4AAFz2=fQRuxvTWQ@mail.gmail.com> <50A5FF83.1060706@lerdorf.com>
In-Reply-To: <50A5FF83.1060706@lerdorf.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] RFC: ext/mysql deprecation
From: streaky@mybrokenlogic.com (Martin Nicholls)

On 16/11/2012 08:55, Rasmus Lerdorf wrote:
> I still don't see the point of using E_DEPRECATED like this for an
> entire extension. And I think it will hurt more than it will help for an
> extension this heavily used. It is going to encourage people to simply
> turn off that warning because they will get it on every single request
> which means they will never see the more subtle and granular
> E_DEPRECATED warnings from other parts of their code.

Catch 22 - if you do nothing people will keep using it, even for new
stuff and progress is never made. This sort of thing is obviously a
horendous nightmare - I personally wonder if flat out shiping it to PECL
with a warning on the PECL page but no E_DEPRECATED might be the better
solution. At least then people who are installing it will be actively
aware they're doing it, without the 'scary' errors spat out when they
connect to a server.

Anybody who needs this will ask their host for it or more likely their
host will already have it installed, but people installing PHP for local
dev machines will probably have to go find it (and the developers are
the target audience for these sorts of things) - which should be enough
to tell them there's something different about this extension, and
they'll see the notice on the site. I honestly can't see a situation
where that would bother people more than keeping it but throwing
E_DEPRECATED fairly often with a view to moving it later anyway - rip
the plaster off in one go so to speak. Maybe PHP has a lot of users that
are somewhat unstable and incapable of using PECL, I dunno ;)