Re: [PATCH] Raise warning first on "Maximum execution time exceeded"
| From: | Johannes Schlüter | Date: | Mon, 22 Mar 2010 15:09:17 +0000 |
| Subject: | Re: [PATCH] Raise warning first on "Maximum execution time exceeded" | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-47447@lists.php.net to get a copy of this message | ||
Hi,
On Mon, 2010-03-22 at 16:00 +0100, Olivier B. wrote:
> well, maybe we should provide a better behaviour for all fatal errors, no ?
> A frequent one I see is the fatal error for calls like "$obj->method()",
> when $obj is not an object.
>
> Isn't possible to allow catching of fatal errors, like other errors ?
Fatal errors might let the engine in some undefined state. The only safe
thing we can do is terminate the current script. fror other cases we
have catchable fatal errors. Maybe there are a few more cases where
fatal errors can be made catchable fatal errors, but these are case by
case decisions.
johannes