Re: Fatal Errors and Error Handling
| From: | Svein Roar Nilsen | Date: | Tue, 24 Apr 2001 10:14:48 +0000 |
| Subject: | Re: Fatal Errors and Error Handling | ||
| References: | 1 2 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-50040@lists.php.net to get a copy of this message | ||
> > And I see no reason why we should not be allowed to handle most of the
> > fatal errors we get on our own. Especially annoying is the xslt_process()
> > function that returns something like "<br><b>Fatal error</b>: XML
> > parser
> > error 7: mismatched tag in <b>/var/www/[...]". As far as I can see, this
> http://www.php.net/manual/en/features.error-handling.php
> have you taken a deeper look into this?
Well, I have tried...
> beside, use @ in front of the command to pipe away the current error or stop
> on-screen display of errors in general.
My problem is that not displaying anything in case of an error is a
completely unacceptable solution. I *MUST* return a valid XML message in
a predefined format. If not, I am violating the standard we are
following. And if I do not find a way to comply with the standard, it
means that we have to scrap PHP alltogether for this project.
Svein Roar