On Aug 22, 2005, at 3:50 PM, Zeev Suraski wrote:
At 20:53 22/08/2005, Marcus Boerger wrote:
> 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?
I'm not sure what happened, but I don't want exceptions at all, let
alone 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.
One of us is missing something, or we're not talking about the same
thing at all.
I'm talking about allowing type hints to be trappable by users,
without complicating them with exceptions. I'm proposing a new
error level, which behaves like E_ERROR, except it can be caught
using a userland error handler, for those cases where the engine/
PHP are in a stable state.
This sounds good to me. We talked about this briefly a year or so
ago, in reference to being able to convert E_ERROR errors to
exceptions in an extension.
George
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
