Re: display_errors in DEV
| From: | Eric Butera | Date: | Tue, 21 Oct 2008 16:41:40 +0000 |
| Subject: | Re: display_errors in DEV | ||
| References: | 1 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-282207@lists.php.net to get a copy of this message | ||
On Tue, Oct 21, 2008 at 12:33 PM, <ceo@l-i-e.com> 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.