On Wed, December 30, 2009 8:30 am, Hans-Peter Oeri wrote: > Hi! > > Christian Schneider wrote: > >> leads to another inconsistency: Depending on the hosting provider >> and/or >> frameworks/modules used you'd have to write different error >> handlers. > > I understand there are widely differing applications for php, that's > why > I think backwards-compatibility and common defaults across > installations > is a must. Changing defaults system-wide is always risky. In a > shared-hosting situation, the proposed error defaults *must not* be > changed, of course.
How exactly do you propose to stop my clients' stupid web hosts from being stupid and changing it, exactly? Cuz I guarantee they'll manage to change it all crazy and make my life miserable. I can see the point of standardizing error handling. But not the point of making it so configurable. And the can of worms you open is that there is simply no agreement on which standard to pick. This is unlikely to have changed with your proposal. Personally, I set up a set_error_handler and set_exception_handler, and if anything I integrate over-rides that, they either do that well and I leave it alone, or they screw it up and I comment it out. But that's just me. -- Some people ask for gifts here. I just want you to buy an Indie CD for yourself: http://cdbaby.com/search/from/lynch -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
