in reply to Re: XML::Expat - error from browser
in thread XML::Expat - error from browser

I found what the issue here is after further consideration. The parse() method is meant to handle both parsing files and strings. If you look at the code that follows that which I included, it tests $ioref to see if there is some kind of filehandle. The line in question (456) is the final attempt to glob a file. The reason that I was seeing it was due to CGI::Carp considering that a fatal error (which the author of Expat.pm doesn't at all). I had to remove the CGI::Carp from the script and handle all my errors myself in an eval{};.
Thanks to everyone who has helped.
BTW, Anonymous Monk, what the heck is absurd about log files being in XML? Works great for me! I can post-process the log file and allow error to be fixed in the browser.
Brian - a.k.a. DrSax

Replies are listed 'Best First'.
Re: Re: Re: XML::Expat - error from browser
by Anonymous Monk on May 29, 2001 at 23:59 UTC
    Sorry about the misunderstanding. *If* you could use *only one* node in a file, *then* it would be absurd to use *that* XML-Implementation for logfiles. I hope that comes across as intended.
Re: Re: Re: XML::Expat - error from browser
by Anonymous Monk on May 30, 2001 at 00:02 UTC
    Everyone is good:-) There was only me. (All Anonymous posts (before this) belong to me).