On Fri, August 10, 2007 10:43 am, Robert Cummings wrote: > On Fri, 2007-08-10 at 11:40 -0400, Daniel Brown wrote: >> On 8/10/07, Stut <stuttle@xxxxxxxxx> wrote: >> > If PHP thinks something might be wrong it will tell you. Why on >> earth >> > would you want to ignore it? You think you're smarter than PHP? >> Really? >> >> Okay, Stut, let's not make Friday the official "Flame Dan Brown" >> holiday this week. I vote that it should be later in the year. >> >> However, it should also be noted that my development is never >> done >> on a production server attached to the Internet, for one; and on my >> development machine, E_NOTICE is always enabled. I just fail to see >> the benefit in alerting visitors to the site that there may have >> been >> something overlooked at some point. > > Why would it alert visitors? You don't have display errors set to on > for > a production server do you? *EEEEEEEEEK*. Send it to a log file. The > reason it's good to enable notices on a production server is because > your visitors are like a horde of testers, they'll probably hit every > nook and cranny of your code that you might have missed during > testing. There are a few billion Google pages that show that way too many web developers have display_errors "ON". I'd STILL say they're better off with E_NOTICE! If they're not bright enough to set things up with errors going to log files, they're DEFINITELY not bright enough to write code without E_NOTICE turned on. :-) -- Some people have a "gift" link here. Know what I want? I want you to buy a CD from some indie artist. http://cdbaby.com/browse/from/lynch Yeah, I get a buck. So? -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
