Re: Re: Fatal errors
| From: | Michael Walter | Date: | Thu, 10 Aug 2006 12:11:30 +0000 |
| Subject: | Re: Re: Fatal errors | ||
| References: | 1 2 3 4 5 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-25286@lists.php.net to get a copy of this message | ||
Hi,
On 8/10/06, Derick Rethans <derick@php.net> wrote:
He wasn't talking about *undefined variables* at all. The variable *is* defined as private and calling that is ofcourse not allowed.I was talking about all kinds of errors which for no good reason are non-recoverable. Surely, the operation being not allowed is a not a a good error to make the error *non-recoverable*.
The second thing is that calling normal undefined functions throws a fatal error as well, and it should do that just like calling non existing methods on an object should throw a fatal error.I'm specifically wondering *why* these errors need be non-recoverable. Ideally, userland would be able to handle them (see the other mails for the rationale). Regards, Michael