For testing, I'm using a form to POST XML to a CGI handler. While developing this, I ran into some problems. It seems that use CGI::Carp 'fatalsToBrowser' is incompatible with XML::Parser. Or maybe I'm making a mistake.

Try this code:

use XML::Parser; use CGI; use CGI::Carp 'fatalsToBrowser'; my $p1 = new XML::Parser(Style => 'Debug'); $p1->parse('<foo id="hi">Hello world</foo>');

Although the parse seems to go fine, CGI reports that a software error occured. Specifically, "Can't use string ("<foo id="hi">Hello World</foo>") as a symbol ref while "strict refs" in use at /usr/lib/perl5/site_perl/5.6.0/i386-linux/XML/Parser/Expat.pm line 456"

If you comment out the 'fatalsToBrowser' line, everything works fine. Is XML::Parser/expat throwing a die call even on a successful parse? Is the parse failing? Am I doing something dumb?


In reply to XML::Parser and CGI 'fatalsToBrowser' incompatible? by fred

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.