On Thu, Nov 15, 2012 at 3:00 PM, Rasmus Lerdorf <ras...@lerdorf.com> wrote:
> On 11/15/2012 11:53 AM, Will Fitch wrote: > > On Thu, Nov 15, 2012 at 2:48 PM, Stas Malyshev <smalys...@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. > > Actually, no it wouldn't. You still get the overhead of the error, plus > any custom error handlers will be triggered regardless of the > error_reporting setting which depending on the implementation of the > error handler can be quite costly performance-wise. > So what solution is there to this? Should it not be deprecated? This same issue (is still happening) with register_globals for us, but it's acceptable as it has been phased out. Should there be no deprecation warning now and wait for a future release? > > -Rasmus > >
