On Thu, Nov 15, 2012 at 3:11 PM, Rasmus Lerdorf <ras...@lerdorf.com> wrote:
> On 11/15/2012 12:08 PM, Will Fitch wrote: > > On Thu, Nov 15, 2012 at 3:00 PM, Rasmus Lerdorf wrote: > > 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? > > I'd like to see usage drop off first so we aren't negatively affecting > millions of sites performance-wise, and/or we streamline the error > handling code so there is a way to avoid this performance hit. > This makes sense, but from an engineering standpoint, what can be used as a trigger to move to a more recent driver outside of deprecation? I'm not sure there is another solution. Your argument is valid. The question of, why do we deprecate something that is so heavily used comes to mind, but in the end, this is a something the extension maintainers want - not end users. Maybe the correct solution is to hand off the maintenance of this extension to a new team? > > -Rasmus >
