Actually, depending on what you're actually trying to accomplish, something other than XML::Parser might be a better fit. In particular, XML::LibXML is vastly superior (IMHO). There's more documentation to look at, but in my experience, it's worth the effort, especially when you get to the XPath stuff.

Here's how I'd use XML::LibXML for that same simple example (to print out just the contents of "Amount" tags): 


#!/usr/bin/perl

use strict;
use warnings;
use XML::LibXML;

my $parser = XML::LibXML->new;
my $doc = $parser->parse_file( "org1.xml" );

my $xpath = XML::LibXML::XPathContext->new( $doc );
for my $node ( $xpath->findnodes( '//Amount' )) {
    print $node->textContent, "\n";
}

[download]
It doesn't get much simpler than that!

In reply to Re: Bug in XML::Parser by graff
in thread Bug in XML::Parser by manunamu

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.