Re: E_ALL changes in 5.2/6.0

On Mon, May 15, 2006 1:59 pm, Marcus Boerger wrote: > yeah we should simply rename the two files we have right now to > that. > I never knew which one to take since their names are not helpful. > In production we would set something like E_ALL & ~E_STRICT & > ~E_NOTICE. > While in development we would do E_ALL as in all. Personally, I've always thought that a smarter setup is to keep E_ALL on all the time, and just turn display_errors off in production, and logging on as an optional in production... But that presumes a quality level in PHP code that's not "out there" yet -- partially because E_ALL wasn't the default for sooooo long, so we had a zillion E_NOTICE messages going un-noticed by the bulk of users. If your production PHP code is generating so many entires in a log file that it's a problem for the log file size, then, really, you've got much bigger problems than the log file size... I can see having the logging off for performance in specific situations, but that would be the people who REALLY know what they're doing anyway. The naive webhost trying to scratch a living out of installing PHP with the default settings and is happy if "it works" is the target audience for the php.ini-recommended -- not the expert than could probably write php.ini from scratch for the settings they care about. YMMV -- Like Music? http://l-i-e.com/artists.htm