> > In Real Life [Patent Pending], if you cripple your production site > in the middle of the night then go to bed, you won't have to worry > about any of this because you'd be unemployed in the morning.
+1... don't commit code without QA! > > I agree with Derick's assessment. > > I always have the option of turning display errors off (which is the > recommendation for production sites) and cranking stuff out to syslog > or some file I can monitor. > > Throwing a 500 document is ugly, and so 90's. :) > Being competitive does not mean 'being like the other guys', a path > PHP has carefully and rightfully avoided. i see your point, but php doesn't really provide a way of halting on all errors, unless you code yourself a funky error handler and well... it gets messy. throwing http 500 is the right way to do it (tm), and i think would be better http conformance if we did. -- james -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
