Am 14/11/12 03:26, schrieb Michael Kliewe: > Am 14.11.2012 00:23, schrieb Ángel González: >> So the problem really moves onto the CMS providers, do they support >> new php versions and drop customers in shared hosting, do they delay >> supporting the new php versions, or do they reimplement mysql_* >> in php? > We are talking about ~1.5 years until ext/mysql is really removed. > Don't you think all big project will be able to remove it during that > timerange? And no big hosting provider will roll out that new version > on day 1, so you will not see many hosters running PHP 5.6 (where > ext/mysql is removed) in the next 2 years. Enough time to get rid of > the old mysql_* things. > > Deprecated warnings do not hurt anybody, in production environments > they are not visible, so where is the problem? Nothing will break with > 5.5 I disagree.
It's not true that they won't be visible in production environments (although they shouldn't). There are scripts doing error_reporting(E_ALL), then not looking at the error_log they are spamming. It's bad if developers disable E_DEPRECATED just to not see this warnings (eg. theyare working in a project which has decided to continue supporting ext/mysql) and due to that miss other deprecated notices. Finally, this is the right time to discuss it. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
