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
Not sure what you mean by (a) but (b) makes sense to me. In any case, we should make a final decision on this issue between B3 and RC1. That is the time to iron out outstanding bugs.
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 ;-)
There seems to be some opposition to this fix. I don't quite understand why but if there is a true need, we might need an additional INI option such as custom_error_handler_error_reporting_mask which would be used.
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 don't think it's that important. In addition, it'll only work for user-land functions. In any case, it is something which could be added but as I really want to see a feature freeze after B3 I suggest it waits for 5.1.
I think the two together would allow some really useful error handling: Error backtraces with detailed information about what happened.
I think the first is something which we should probably solve for 5.0 especially with the added errors E_STRICT creates.
Andi
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
