Re: [PHP] Error checking ON
[email protected] (Jim Lucas)
| Newsgroups | php.general |
|---|---|
| Message-ID | <[email protected]> |
On 07/17/2013 09:28 AM, Tedd Sperling wrote: > On Jul 17, 2013, at 11:55 AM, Daniel Brown <[email protected]> wrote: >> On Wed, Jul 17, 2013 at 11:49 AM, Tedd Sperling <[email protected]> wrote: >>> This is what I do for error checking: >>> >>> ini_set('error_reporting', E_ALL | E_STRICT); >>> ini_set('display_errors', 'On'); >>> ini_set('log_errors', 'On'); >>> ini_set('error_log', 'error_log'); >>> >>> Is this: >>> >>> 1. Sufficient? >>> >>> 2. An overkill? >>> >>> 3. OK? >>> >>> 4. OR, better served with this (and provide an example). >> >> That's standard practice. Sometimes, though, it isn't enough, and >> we find ourselves using Derick's Xdebug, mod_top, or performing an >> strace on either the execution or attached to a process. For nearly >> all cases, though, that's sufficient without being overkill (except >> for production cases). >> > > Daniel: > > Thanks -- I always wondered about that. > > Cheers, > > tedd > > PS: Of course, turned OFF for production. :-) > > _____________________ > [email protected] > http://sperling.com > But... It won't work in all cases. I find it best to set these settings in the server itself. Not in code. Sometimes, if you have broken code that cannot be parsed, your commands listed above will never be executed. Therefor they will never do any good. -- Jim Lucas http://www.cmsws.com/ http://www.cmsws.com/examples/