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
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.