Man i love php more and more every day.... I only wish it didn't take me this long to find what i needed to do.....
if anyone cares you can set the zend_error_cb to what ever cb you want. wich will allow you to control all errors. zend_error_cb = my_new_cb; and all is good :).. If anyone who acually knows the zend engine really good they can tell me if i should or shouldn't do this. - Brad --- brad lafountain <[EMAIL PROTECTED]> wrote: > Hello, > > I am writing an extension which i NEED absoulty control over what goes > out of > a php script meaning all errors and all output. I can caputre all > outputs with > ob* functions but im having problems with error handling. I use the > user > defined error handling wich doesnt get the level of control that i > want. > because it doenst let the user capture > > case E_ERROR: > case E_PARSE: > case E_CORE_ERROR: > case E_CORE_WARNING: > case E_COMPILE_ERROR: > case E_COMPILE_WARNING: > > So what are the possible soulitions.. let the user caputre these errors > or being able to override the default zend_error_cb() with your own > defined > callback?? > > - Brad > > > __________________________________________________ > Do You Yahoo!? > Great stuff seeking new owners in Yahoo! Auctions! > http://auctions.yahoo.com > > -- > PHP Development Mailing List <http://www.php.net/> > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > To contact the list administrators, e-mail: [EMAIL PROTECTED] > __________________________________________________ Do You Yahoo!? Great stuff seeking new owners in Yahoo! Auctions! http://auctions.yahoo.com -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
