Re: Fatal errors
| From: | Michael Walter | Date: | Thu, 10 Aug 2006 10:54:58 +0000 |
| Subject: | Re: Fatal errors | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-25280@lists.php.net to get a copy of this message | ||
Yeah. It is problematic that the application has no chance of dealing
with the errors itself (consider e.g. php-shell which has to go great
lengths to prevent fatal errors from user code leading to php-shell's
termination, and still fails at doing this in the general case).
Regards,
Michael
On 8/10/06, Lukas Kahwe Smith <lsmith@php.net> wrote:
Michael Walter wrote: Hi, right now, PHP triggers fatal errors e.g. when accessing private members or calling nonexistant functions. Since this is problematic for obvious reasons, what technical reasons are there for that behavior, and is there a chance that this behaviour will change in a future release? what is "problematic" here? Are you simply suggesting to make them E_RECOVERABLE since they do not really leave the engine in a broken state? regards, Lukas