Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:63884
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain meetme.com designates 74.125.149.250 as permitted sender)
MIME-Version: 1.0
Sender: wfitch@meetme.com
In-Reply-To: <50A54713.8090102@sugarcrm.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>
	<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>
Date: Thu, 15 Nov 2012 14:53:24 -0500
Message-ID: <CAArmra2bjj3y2UUV8nszU74tN9o4VvB67aXzq5Z1cE2Y_tVijg@mail.gmail.com>
To: Stas Malyshev <smalyshev@sugarcrm.com>
Cc: Adam Harvey <aharvey@php.net>, Devis Lucato <devis@lucato.it>, 
	PHP Developers Mailing List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=14dae9ccd52c037e7d04ce8e01f1
Subject: Re: [PHP-DEV] RFC: ext/mysql deprecation
From: willfitch@php.net (Will Fitch)

--14dae9ccd52c037e7d04ce8e01f1
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Nov 15, 2012 at 2:48 PM, Stas Malyshev <smalyshev@sugarcrm.com>wrote:

> Hi!
>
> > Again, though, this is a long way down the road: today's discussion is
> > purely about deprecation.
>
> So these people using mysql-based code will have for years to live with
> applications generating thousands of warnings and not be able to do a

thing about it? How is it good for them?
>

I don't mean to state the obvious, but wouldn't display_errors = 'Off' in
production or error_reporting = E_ALL ^ E_DEPRECATED be sufficient?  This
is the same approach taken with register_globals - and it happened between
5.3 and 5.4.



> --
> Stanislav Malyshev, Software Architect
> SugarCRM: http://www.sugarcrm.com/
> (408)454-6900 ext. 227
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--14dae9ccd52c037e7d04ce8e01f1--