Yeah this is a known bug and will have to be fixed in RC1. It's not a showstopper for B3.
Yes, this bug has indeed nothing to do with B3. I just though that PHP5 would maybe be the time to make set_error_handler finally usable.
In any case, I do think that the custom error handler being called for any error is bogus. Why should E_STRICT or E_NOTICES be sent to the handler if they are off?
I agree wholeheartedly, especially since one can set reporting to E_ALL and then ignore whatever one likes but with the way it is now there is no way of not being called for everything.
If you want I could provide patches which
a) fix the above bug (the person in charge told me that they're working on a more thorough solution to the problem but I haven't heard anything since).
b) only calls the custom error handler when that error type is on
Just tell me _when_ I should submit it, as everytime I submitted something so far I was told it couldn't be accepted at that point because a release was about to happen ;-)
While I'm at it: Is there any chance my idea of adding the local variables to debug_backtrace could be implemented in PHP5? I'm willing to provide the implementation, I could also make it optional if you want.
I think the two together would allow some really useful error handling: Error backtraces with detailed information about what happened.
- Chris
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
