#50446 [Opn]: Missing documentation or bug for SET_EXCEPTION_HANDLER()

ID: 50446 User updated by: randallgirard at hotmail dot com Reported By: randallgirard at hotmail dot com Status: Open Bug Type: Documentation problem Operating System: Windows PHP Version: 5.3.1 New Comment: Oops I forgot to supply the link, here ya go: http://bugs.php.net/bug.php?id=50454 Previous Comments: ------------------------------------------------------------------------ [2009-12-11 20:11:40] randallgirard at hotmail dot com I added a new bug for feature request at the following, explaining more of a WHY reason for such a situation. Mainly in my situation though, is because I am combining SET_ERROR_HANDLER with SET_EXCEPTION_HANDLER, and the ERROR_HANDLER fires ErrorException, as noted in the documentation. Therefor, even though my ERROR_HANDLER processes the $errnum correctly, script execution still terminates when for example E_USER_NOTICE or E_USER_WARNING happens, and no way for me to write a work around for this. ------------------------------------------------------------------------ [2009-12-11 20:10:46] bjori@php.net replace that "*must*" with an RCC2119 SHOULD ------------------------------------------------------------------------ [2009-12-11 20:08:09] bjori@php.net To process *unhandled* exceptions. If your application throws an exception you don't expect, then you *must* have an exception handler that catches that exception, logs it, and prints a pretty error page for your user. Maybe we should add a tip or a better usecase/description? (re-opening) ------------------------------------------------------------------------ [2009-12-11 19:41:00] randallgirard at hotmail dot com What is the reason for this functionality, if you cannot return to processing of the script? ------------------------------------------------------------------------ [2009-12-11 09:55:54] rquadling@php.net As does the Description ... "Execution will stop after the exception_handler is called." Nothing additional required. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/50446 -- Edit this bug report at http://bugs.php.net/?id=50446&edit=1