Mathieu Gagné wrote: >> I personally also don't see a good reason to disable E_WARNING and >> E_NOTICE (and possibly also E_DEPRECATED) in a production environment - >> you may still want to log such errors. As long as display_errors is >> off, it's not a problem except for the performance hit which should be >> low assuming you don't have too many of them. > > As a system administrator, I must disagree with your opinion as most > users don't care about error_log file. I have see a lot of servers with > about 6GB of error_log filled with E_NOTICE AND E_WARNING.
I would consider this the sysadmin's fault for letting logs grow without bounds. Surely you have heard of log rotation? > Just letting it enabled by default in production is a bad idea. Those > notices should only be enabled during development since production is no > more the time to do such debugging. If you have debugged your code well, and got rid of all the E_WARNING/E_NOTICE that you can, then surely you would want to know if a new one crops up? I see no problem with having E_WARNING/E_NOTICE enabled. E_DEPRECATED is another thing though. Enabling this by default is good because you will notice when code you are using becomes deprecated. However it probably shouldn't be enabled in production as you should be upgrading PHP on a development/testing/staging system before you do so on a live server! -- Jasper Bryant-Greene Director Album Limited [EMAIL PROTECTED] +64 21 708 334 / 0800 425 286 http://www.albumltd.co.nz/ -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
