Re: Exceptions and Errors
| From: | Jevon Wright | Date: | Tue, 13 Apr 2004 23:05:12 +0000 |
| Subject: | Re: Exceptions and Errors | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-9133@lists.php.net to get a copy of this message | ||
> Your example is interesting. It shows an error that would be continuable
> from an engine's point of view but not from the script's point of view. It
> shows that there should not be any possibility to recover from exceptions
> at the exact spot where the exception was thrown - anyway somthing that
> violates the general exception idea (see Stanislav's mail on local stack
> corruption...).
Java has the concept of an "Error" (extended from Throwable which is
extended to be Exception too) which "indicates serious problems that a
reasonable application should not try to catch. Most such errors are
abnormal conditions."
Perhaps normal E_ERROR => Exception, and totally fatal errors => Error. You
can catch Errors too, but it's specifically said that you really shouldn't
try.
Jevon