On Thu, Nov 15, 2012 at 3:11 PM, Anthony Ferrara <ircmax...@gmail.com> wrote: > Will, > > >> 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? >> > > That's my suggestion. Officially deprecate it, but don't add E_DEPRECATED > to it in 5.5. Update the documentation, and start a PR campaign to get off > it. Then in NEXT add E_DEPRECATED and in NEXT+1 remove it. But I've said it > a number of times, and it appears that I'm the only one who thinks that > it's a good idea to take it slow and give users time to move off it... > > Anthony
You see, I'm skeptical about this approach. Mainly because I don't see how any of that has proven to be the case in the past. Albeit, we've never deprecated such a heavily used extension before in the past, but still. There remains the issue of "how many people will actually read the manual" vs. "how many will take this as a precursor to either stop using the extension in development of new applications (we already advice against that now in the manual by the way)" vs. "how many will take action to not upgrade or fix their legacy code" vs. "how many people actually intend on upgrading to PHP 5.5 when they have legacy code dependent on ext/mysl". I think these questions need to be considered more seriously in order to re-evaluate the proposal of "delaying E_DEPRECATED for ext/mysql is really going to help people". Does any of this really help anyone affected by the deprecation of the extension? I can't possibly see how since those that are still using it will just likely not upgrade to PHP 5.5 if their legacy code can not due without ext/mysql. Your not considering the sheer number of projects that still haven't upgraded from 5.3 let alone 5.4. I really urge everyone reconsider the reality of delaying the warnings and what good that actually brings. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
