>hmm, I really thought we didn't have one, as it doesn't make sense at >all :)
Ha! I'm not crazy! :) >>Having a solid way to >> gracefully bow-out because my cat managed to open, fill with >junk, and >> save a critical include file would just be nice. The choice between >> the blank screen, or a nasty error message isn't a good one... I'd >> personally love to have a "sorry, our site is hosed" error >page... If >> for nothing else then piece of mind... > >Your cat knows your passwords? :) Anyway, you can always use the >error_append_string and error_prepend_string for this. (by >putting <!-- >in prepend_string and --> in append string for example). Not true. All I've done in that case is display a half-completed page And hide the fact it died in a comment. Not to mention that doesn't allow For any sort of e-mailing me to let me know my cat hacked my account again (she's a smart little bugger). I guess I just really do believe that PHP's Error handling mechanism has little real use in its current form. There are Better methods of dealing with logic-errors than using trigger_error() if The only thing they are good for is logic-errors... However, If I could handle Every single error that didn't cause some catastrophe seg-fault I feel that It would add a nice capability to the language. Hence, I am still standing by my re-direct (with GET parameters for the nature Of the error :)) suggestion :) John (and his cat) -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
