With small files (say, < 100MB) , I usually just load the whole thing in, and then get all the elements I'm interested in, and work on them - I find it easier than the stream interface. However, in your case, we might be stretching it unless you've got a 64-bit perl. So here's a stream example. Note that for your example, I just put the whole thing in "<something>..</something>" tags so it'd be valid XML.

use strict; use warnings; use XML::Twig; my $twig = XML::Twig->new( twig_handlers => { offer => sub { printf("%s,%s,%s\n", $_->att('id'), $_->first_child('f1')->text() +, $_->first_child('f2')->text() +, ); } } ); $twig->parsefile('a.xml');

Hope that helps


In reply to Re: example for parseing xml with xml::twig by Tanktalus
in thread example for parseing xml with xml::twig by Anonymous Monk

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.