Re: exceptions instead of errors
| From: | (Marcus Börger) | Date: | Tue, 13 May 2003 19:28:26 +0000 |
| Subject: | Re: exceptions instead of errors | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-1488@lists.php.net to get a copy of this message | ||
At 18:45 13.05.2003, Zeev Suraski wrote:
Unless I'm missing something Marcus' patch only deals with non fatal errors. But if I am missing something and it somehow tries to be smart about E_ERRORs - it shouldn't, whether or not an error is fatal should be left entirely to the author of the error call...Atm the following error cannot be turned into an exception, all others can be. E_ERROR E_CORE_ERROR E_COMPILE_ERROR E_USER_ERROR E_PARSE The reason i did not allow E_ERROR is the fact that i knew some few errors which leave an unstable engine state. So perhaps a new error code isn't such a bad idea as i first thought. But it makes only sense when we change some codes which are aren't really E_ERROR and that would be another BC issuue since it would also affect non exception code. OR we convert the new error code into its original E_ERROR code before spitting it out as a normal error. marcus