XML::LibXML also offers much simpler and clearer interface than XML::Parser. I'd never use XML::Parser directly; at the least, you need XML::Twig to get any work done.

Another serious reason in favour of libxml, which is much more practically important than its performance, is that consumes much less memory — a huge win when you're working with larger XML files. (It's no fun when your Perl processes grow to 600MB to generate a mere 40MB XML file.)

On unixoid systems, the dependencies are not likely to be a problem either. I don't know if there's a PPM for Windows people, but if so, that should work with a minimum of fuss for them.

Makeshifts last the longest.

In reply to Re^2: Perl xml parser by Aristotle
in thread Perl xml parser by Nalina

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.