OK, apparently we will continue the discussion her. Pierre Joye in php.internals (Wed, 5 Sep 2012 13:15:43 +0200): >On Sep 4, 2012 10:25 PM, "Jan Ehrhardt" <php...@ehrhardt.nl> wrote: >> >> Rasmus Lerdorf in php.internals (Tue, 04 Sep 2012 13:15:50 -0700): >> >Just call error_reporting() at the beginning of your script. >> >> Which ain't possible in drupal (or hardly). You do not write any code. >> You just click together modules, written by others. > >.htaccess (or pecl's htscanner for fcgi and 5.2), .user.ini (5.3+) >will both let you do that easily.
No, it will not, because bootstrap.inc overrides the php.ini settings as well as the .htaccess settings. >And patching bootstrap.inc is still acceptable. You do not want to patch drupal's core yourself. Too much chance your patch gets lost at every minor update. And besides that you'll have to revert your own patches if you run into a problem and want to discuss it on drupal.org. > While it is not >necessary if you don't mind too much about the noises in your error >logs :) On a development server you want to see the warnings on screen, without all those E_STRICT warnings. And the noise will degrade the already low performance of a drupal7 system. Quote from http://drupal.org/node/1267246 "This incurs a significant performance overhead for error handling whenever a notice occurs, as well as a lot of useless noise in Drupal's watchdog log (and even on screen if error logging to screen has not been disabled), and given that these are mostly coding style issues and not indicative of any real problem." Jan -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
