Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:63916
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain roshambo.org from 209.85.210.42 cause and error)
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <50A5FF83.1060706@lerdorf.com>
Date: Fri, 16 Nov 2012 01:25:03 -0800
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>
Content-Transfer-Encoding: 7bit
Message-ID: <B6638662-0DFB-4679-AEFD-BA8A51DDCD1F@roshambo.org>
References: <CADajX4CYZdNpgQv46m_6J7tQLBc=h6HxCn-bGpxr3Ou2VaqgBg@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> <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>
To: Rasmus Lerdorf <rasmus@lerdorf.com>
Subject: Re: [PHP-DEV] RFC: ext/mysql deprecation
From: philip@roshambo.org (Philip Olson)


On Nov 16, 2012, at 12:55 AM, Rasmus Lerdorf wrote:

> On 11/16/2012 12:51 AM, Patrick ALLAERT wrote:
>> Rasmus,
>> 
>> As per the RFC: adding E_DEPRECATED only in mysql_connect(),
>> mysql_pconnect(). Which means only one error (normally) by request.
> 
> 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.

Most front page google results for "E_DEPRECATED" are questions about 
how to hide these errors. This thought has put me over the edge and 
into the land of not having E_DEPRECATED for ext/mysql in 5.5. Let us 
prepare for this first as we are not ready. Seriously, we are not ready.
And it makes me wonder about "E_DEPRECATED" as a whole.

But this seriously makes me wonder if we should add something like 
how_do_i_make_my_code_more_awesome(). That may look insane (well, the
function name is) but imagine it saying "Stop using ext/mysql" and
then users hear about this, run it, and ask Wordpress "Dude, this
would be more awesome without ext/mysql" and so on. Brainstorming. :)

Regards,
Philip