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.
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. Regards Mike Robinson Ivan Ristic writes: > Edin Kadribasic wrote: > > > On Thursday 21 November 2002 08:04, Derick Rethans wrote: > > > > >I still think that an included file just should fail hard > and I just > > >dont like this kind of obfucsication. > > > > > > I agree with this 100%. It is IMHO a complete waste of time > trying to > > handle parse errors gracefully. Most "solutions" proposed in this > > thread are either server specific or would have an impact > on normal > > php operation (would require output buffering, etc.). > > And in the real life you sometimes must change things live > on the server, in the middle of the night. If you make a > mistake then, and we all do, you will go to sleep without > realising that the app/web site no longer works properly. > > I use logwatch for this at the moment, but that is, IMHO, a > very, very, clumsy solution. -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
