-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 Steph Fox wrote: >> Ones again E_ALL is for development. For example to move PEAR code to >> PHP 5. >> It is not for running legacy apps. IF you guys want i'd be ok with >> adding a >> new mode say "E_RUN"... > > You think that - I think that. After Brian Moon's response I went and > checked what the INI files distributed with PHP actually say. > > ini-dist is set at E_ALL & ~E_NOTICE > ini-recommended is set at E_ALL > > I'd guess that's why Brian reports seeing E_ALL enabled on web hosts; > they're advised to use the settings in ini-recommended, after all.
I see nothing wrong with E_ALL enabled on a production web server - I administer a very busy web server running a large PHP application, and have error_reporting set to E_ALL | E_STRICT. Of course, I do not have display_errors on. Pretty much the only errors I ever get logged are from PEAR, and I have a system to strip these out at the logger level. Jasper -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEaOvYFfAeHhDzT4gRA2QUAJ9ERKmtU7fpGcKmbvzOiZSqnTr1pQCcC3S2 trR/ddzI0bZfmyfmZN0ET1w= =m6k4 -----END PGP SIGNATURE----- -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
