I would propose not to use create_function() but a static function Zend_Exception::handleError() which handles as the error handler. Except that this seems to be a great proposal.

I have didn't thounght about it. I agree that static function Zend_Exception::handleError() will be much better. I'll update skeleton according to your suggestion.

I don't think it should be placed under Zend_Exception, but rather Zend_Error because an error handling system could be developed more flexible that way. Restricting it to Zend_Exception would not be ideal.

I'd like to see the ability to pass severity levels to the handleErrors method to allow more fine-grained control

E.g. handleErrors($severity = E_ALL)

So you could potentially pass Zend_Exception::handleErrors(E_ALL & ~E_NOTICE | E_WARNING);

I can't see the point in a Zend_Error component - if you wished to handle errors in a more specific way you'd no doubt be creating your own classes to deal with that?

I don't think that it has to be placed into independet class such as Zend_Error, just because Zend_Exception is the "core" of error handling in framework and this proposal is just makng Zend_Exception able to serve almost all errors happened in application.

But in other hand, I think there is a place for Zend_Error class, just in the role of decorator. So it can be used to handle exceptions in common way or something like this. But, as Simon noticed: "if you wished to handle errors in a more specific way you'd no doubt be creating your own classes to deal with that". So IMHO even if there will be Zend_Error it will be just a wraper to do tricks with exceptions and errors.

Alexsey, is this proposal ready for community review?

,Wil

Note that in its current form this proposal is incompatible with the built-in translation functionality of Exception codes in exceptions - Matthew Ratzloff & Thomas Weidner.

Wouldn't it be problematic if someone is already using his own error_handler ?
You can only set one error_handler at once.

Wouldn't it be better to have exceptions and errors seperated ?

An exception can be handled by the application.
An error would need a completly different usage to be handled.

Also as already mentioned, the output can not be translated so all logs must be in english which does not take in account all non-native english people.

I was thinking about what Thomas Weidner said about "separating flies from cutlets" and idea stikes me.

The best way is to separate this proposal to Zend_Exception_Error

So one part (constructor for example) of this proposal will migrate to Zend_Exception_Error
and another part (static methods of setting error_handler) will stay in Zend_Exception.

This way will help to integrate this proposal into current structure easily and without any additional modifications (So integration with Exception codes in exceptions - Matthew Ratzloff & Thomas Weidner will become transparent). )

Shouldn't the default value for $error_types only contain errors (E_USER_ERROR and E_RECOVERABLE_ERROR)? Everything else is not really an error and shouldn't even happen in deployed code.

Archiving this proposal, feel free to recover it when you want to work on it again. For more details see this email.