Re: E_ALL changes in 5.2/6.0

From: Date: Mon, 15 May 2006 21:55:32 +0000
Subject: Re: E_ALL changes in 5.2/6.0
References: 1 2 3 4 5 6  Groups: php.internals 
Request: Send a blank email to internals+get-23429@lists.php.net to get a copy of this message
On Mon, May 15, 2006 2:19 pm, Marcus Boerger wrote: > This is very true, yet i don't see a reason to include E_NOTICE and > E_STRICT > on a production machine. You've got 100% code coverage with all possible inputs and boundary conditions in your QA process?... Cuz, if not, I really don't see why you'd turn these OFF... Unless, like, you actually send code of to production complete with un-debugged E_NOTICE and E_STRICT messages that would flood your log files... [shrug] At that point, I'd say "logrotate more often" before I'd say turn off E_NOTICE or E_STRICT. Maybe I'm just naive... -- Like Music? http://l-i-e.com/artists.htm

« previous php.internals (#23429) next »