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 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
