NYCPHP Meetup

[Jeff Siegel - PHundamentals]

I don't think you want errors appearing at all though I'm often 
surprised how many times I've seen Cold Fusion sites display all their 
errors (and path info, etc.) right there for the world to see.

The warning about sending errors to the browser (at least during 
development) is not that it's the worst thing in the world but that 
there are times when an error message could have some characters that 
won't display properly in a browser but, of course, you can read just 
fine in a log file.

Jeff

Mark Armendariz wrote:

> You could do what Cold Fusion does, which is spit out a huge list of closing
> tags before it spits out an error.
> 
> 
>>-----Original Message-----
>>From: talk-bounces at lists.nyphp.org [mailto:talk-bounces at lists.nyphp.org]
>>On Behalf Of csnyder
>>Sent: Tuesday, November 23, 2004 5:30 PM
>>To: NYPHP Talk
>>Subject: Re: [nycphp-talk] (no subject)
>>
>>Actually they can wind up in all sorts of weird places if you try hard
>>enough. Nothing like a PHP error in the middle of some javascript to
>>break your interface...
>>_______________________________________________
>>New York PHP Talk
>>Supporting AMP Technology (Apache/MySQL/PHP)
>>http://lists.nyphp.org/mailman/listinfo/talk
>>http://www.newyorkphp.org
> 
> 
> 
> _______________________________________________
> New York PHP Talk
> Supporting AMP Technology (Apache/MySQL/PHP)
> http://lists.nyphp.org/mailman/listinfo/talk
> http://www.newyorkphp.org
>