hi Jan, On Thu, Nov 29, 2012 at 4:46 PM, Jan Ehrhardt <php...@ehrhardt.nl> wrote: > Kris Craig in php.internals (Wed, 28 Nov 2012 12:33:55 -0800): >>We also know that E_DEPRECATED works when other approaches do not. I would >>point you all to the famous example of Drupal 7, which would break >>completely due to a flurry of E_DEPRECATED warnings (if display_errors was >>set to on) being triggered as of 5.3 due to their continued use of >>magic_quotes_gpc and magic_quotes_runtime. When Drupal 8 was released some >>time later, the code was fixed so that it no longer used those out-dated >>functions. > > http://drupal.org/community-initiatives/drupal-core > Drupal 8 will not be released before August 2013. Maybe in the current > core the E_DEPRECATED warnings are gone, but certainly not in many of > the modules.
Drupal 7 supports PDO. There is no such thing like mysqli or mysql as driver. > People are still switching to Drupal7. And Drupal7 throws the watchdog > full with E_DEPRECATED warnings when it is running onder PHP5.4. The > views module has issues with PHP 5.4, but some modules even let Drupal7 > under PHP5.4 crash completely: > http://drupal.org/node/1831402 If there is a crash, a bug at bugs.php.net should be reported. > If E_DEPRECATED stays in ext/mysql even after it has moved to PECL, the > result will be that more and more people turn E_DEPRECATED warnings off. And? Where is the problem? The idea is to have it on in dev not in prod. Cheers, -- Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
