Re: [RFC] E_DEPRECATED

On 24/10/06, Mathieu Gagné <mgagne@generationphp.net> wrote:

Hi, 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. 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.

As I run my own servers, I'm forgetful of the laziness of some ISPs. So, yes I can see that having them enabled COULD be considered a bad thing, BUT again, it is education to train people to write code which doesn't produce WENDS (Warnings/Errors/Notices/Deprecated/Strict). And for those lazy ISPs, it will make little difference what the setting is anyway. If they have a 6GB error file now, then having one a little bigger really isn't that much of concern. The benefit though is that WENDS can still be generated in a production environment and I would sure as hell want to see them in a log file. Often the production environment is not 100% identical to the development environment (different memory, speed, loading, etc). Or to paraphase Forrest Gump, "Shit Happens!". -- ----- Richard Quadling Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&amp;r=213474731 "Standing on the shoulders of some very clever giants!"