On Wednesday 25 April 2001 13:32, Svein Roar Nilsen wrote:
[...]
> This is quite similar to what I am trying. If you now corrupts the
> xmlData variable, e.g. by changing to without
> changing the closing tag, you will get an error message saying
>
>
> Fatal error: XML parser error 7: mismat
"Christian Reiniger" <[EMAIL PROTECTED]> wrote in message
01042417490700.07614@chrisbig">news:01042417490700.07614@chrisbig...
>Well, "needed to use" might be incorrect, because return value evaluation
>can be used instead (unless some functions never signal errors via their
>return value). Aside
On Tuesday 24 April 2001 17:14, Boget, Chris wrote:
> > > > > > if (@foo_bar (42, 4711) == ERROR_CODE) {
> > > > > >PrintXMLErrorMessage ();
> >
> > Well, we both are right. The snippet I suggested (top of this mail)
> > *will* work, because the @ operator doesn't mess with the return
> > valu
> > > > > if (@foo_bar (42, 4711) == ERROR_CODE) {
> > > > >PrintXMLErrorMessage ();
> Well, we both are right. The snippet I suggested (top of this mail)
> *will* work, because the @ operator doesn't mess with the return
> value of the function.
That is correct. However, the "== ERROR
On Tuesday 24 April 2001 16:48, Boget, Chris wrote:
> > > > standard we are
> > > > if (@foo_bar (42, 4711) == ERROR_CODE) {
> > > >PrintXMLErrorMessage ();
> Wrong back. From:
> http://php.net/manual/en/function.set-error-handler.php
>
>
> It is important to remember that the standard
> > > standard we are
> > > if (@foo_bar (42, 4711) == ERROR_CODE) {
> > >PrintXMLErrorMessage ();
> > I do not believe the above will work. When using the "@" symbol
> > in front of an expression, it makes it so that the error
> > code that is returned is "0". While writing my error handle
On Tuesday 24 April 2001 14:47, Boget, Chris wrote:
> > > 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
> > if (@foo_ba
> > 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
> if (@foo_bar (42, 4711) == ERROR_CODE) {
>PrintXMLErrorMessage ();
I d
Geir Eivind Mork wrote:
> > > http://www.php.net/manual/en/features.error-handling.php
> > > have you taken a deeper look into this?
> > Well, I have tried...
> And what kind of problem did you encounter?
The problem is that PHP generates fatal errors too often, and I have not
been able to f
On Tuesday 24 April 2001 12:14, Svein Roar Nilsen wrote:
> > 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
> > http://www.php.net/manual/en/features.error-handling.php
> > have you taken a deeper look into this?
> Well, I have tried...
And what kind of problem did you encounter?
> My problem is that not displaying anything in case of an error is a
> completely unacceptable solution. I *MUST* re
> > 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 "Fatal error: XML parser
> > error 7: mismatched tag in /var/www/[...]". As far as I can see, this
>
On Monday 23 April 2001 17:29, Svein Roar Nilsen wrote:
> 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 "Fatal error: XML parser
> error 7: mismatched tag
13 matches
Mail list logo
