[PHP] display_errors in DEV
Until recently, I've thought that display_errors in DEV was good But as soon as you move into Ajax Web 2.0 world, it really doesn't cut it. You'll never see the E_NOTICE and E_WARNING errors for Ajax, probably, and the whole thing might just work but you'll have plenty of buggy code. I think it's time for the PHP team to recommend log_errors across the board. What do you think? -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] display_errors in DEV
On Tue, 2008-10-21 at 16:33 +, [EMAIL PROTECTED] wrote: Until recently, I've thought that display_errors in DEV was good But as soon as you move into Ajax Web 2.0 world, it really doesn't cut it. You'll never see the E_NOTICE and E_WARNING errors for Ajax, probably, and the whole thing might just work but you'll have plenty of buggy code. I think it's time for the PHP team to recommend log_errors across the board. What do you think? Have a simple switch for ajax requests so errors to go into a file... or send the errors along as part of the ajax request and have the ajax code popup a warning that is readable. Or whatever :) Cheers, Rob. -- http://www.interjinn.com Application and Templating Framework for PHP -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] display_errors in DEV
On Tue, Oct 21, 2008 at 12:33 PM, [EMAIL PROTECTED] wrote: Until recently, I've thought that display_errors in DEV was good But as soon as you move into Ajax Web 2.0 world, it really doesn't cut it. You'll never see the E_NOTICE and E_WARNING errors for Ajax, probably, and the whole thing might just work but you'll have plenty of buggy code. I think it's time for the PHP team to recommend log_errors across the board. What do you think? -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php This has bit me in the bum several times. What I do though is put a try catch around my json response parsing and if something goes wrong then I show some error to the user. Then with firebug I can see the raw php error. So I guess I don't care either way since I'm covered. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP] display_errors in DEV
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 21, 2008 11:33 AM To: php-general@lists.php.net Subject: [PHP] display_errors in DEV Until recently, I've thought that display_errors in DEV was good But as soon as you move into Ajax Web 2.0 world, it really doesn't cut it. You'll never see the E_NOTICE and E_WARNING errors for Ajax, probably, and the whole thing might just work but you'll have plenty of buggy code. I think it's time for the PHP team to recommend log_errors across the board. What do you think? Report via Javascript exceptions. If you're debugging with your browser (i.e., Web Developer plug-in for Firefox, or even the plain, built-in debuggers will do) you should be able to view the exception's message and maybe even a stack trace if you set it up right. Todd Boyd Web Programmer -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
