Re: Exceptions and Errors
| From: | Ferdinand Beyer | Date: | Mon, 12 Apr 2004 10:13:42 +0000 |
| Subject: | Re: Exceptions and Errors | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-9053@lists.php.net to get a copy of this message | ||
On 12 Apr 2004 at 12:05, Andi Gutmans wrote:
> I agree it's a problem, but as you know, for BC reasons we can't
make all
> internal functions throw exceptions. I do suggest however, that
new object
> oriented extensions throw exceptions in object context. This isn't a
BC
> break and makes sense as it's used in an object-oriented context.
> In any case, I understand that throwing an exception from user-
land error
> handling works as expected so this can partially solve the problem
with
> internal functions too.
>
> Andi
The problem with exception thrown by a user-land error handler is to
distinguish real exceptions that break the execution from informative
warnings.
I have just experienced this while playing around with XML Schema
validation and 5.0.0b4. The current implementation always triggers
two warnings telling 'Unimplemented block at xmlschemas.c:2245'.
Furthermore, every validation failure is reported using PHP warnings.
That's why it is impossible to use a "user-land exception thrower"
with schema validation at the moment. I don't know if it is the only
extension misusing the errror handling mechanism...
--
Ferdinand Beyer
<fb@fbeyer.com>