Hello Zeev, Monday, August 22, 2005, 1:38:54 PM, you wrote:
> At 14:34 22/08/2005, Derick Rethans wrote: >>On Mon, 22 Aug 2005, Zeev Suraski wrote: >> >> > >It seems most are for >> > >another type of error that are fatal if not "handled" in the user error >> > >handler. There is just one thing... how do we signal it back from the >> > >handler? Currently there is no defined return value for the user defined >> > >error handler. I suggest that if you return "false" from the user >> > >defined error handler than that signals that PHP should handle the error >> > >(and this stop the application in case the new error type was thrown). >> > >> > I'm not exactly following. If you want to stop the application, why >> wouldn't >> > you simply exit()? >> >>I *don't* want to stop it :) > So in that case, the implementation in zend_error_cb() should simply call > the user error handler if it's available, or treat it as if it's E_ERROR if > there is no user error handler. Isn't an E_ERROR by default good enough or do you want exceptions here always? In the former case it might be better to have a new error level E_HINT. In the latter case maybe it might be a good idea to move the default exceptions from ext/spl to the engine and have a 'Hint' whatever exception class derived from RunTimeException. Best regards, Marcus -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
