You should be OK with most XML modules, but if you really need to conserve memory then i recommend looking into event based parsers like SAX rather than tree based parsers. A quick google search yielded this document which does a pretty good job of explaining the difference: http://www.informit.com/articles/article.aspx?p=27006&seqNum=7&rll=1

L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
B--B--B--B--B--B--B--B--
H---H---H---H---H---H---
(the triplet paradiddle with high-hat)

That article is six years old. And is written as if DOM and SAX were the only contenders. soliplaya, have a look at XML::Twig and XML::Rules. The first is often recommended here, the second is mine :-) and a nice combination of event and tree based parsing.

Jenda


Support Denmark! Defend the free world!

Thanks Brothers.
Jenda, your XML::Rules module look interesting, and I'd like to give it a try.
What I need to do is fairly simple and boring : I need to parse a multi-level XML document, contained in the scaler $xmldoc, representing a Journal Article (*), into a simple hash like


my $href = {
  'TI' => [ 'content of <PubArticle><Article><Title> tag' ],
  'AU' => [ 'content of <PubArticle><Article><Authors><Author name="au
+thor1" tag',
            'content of <PubArticle><Article><Authors><Author name="au
+thor2" tag',
            etc.. ],
  'REF' => [ and so on... ]
};
[download]


The end-result I want thus, is a hash in which each key corresponds to an arrayref, the array containing one or more string elements, these being picked up from tag attributes and/or values from the original XML document. I admit I am a bit lost after the first read of the on-line doc. I guess what I don't see very clearly, from the first example at the head of the doc, is how I get the result in my $href hash.
(*) for a full example of the source XML, use this link : http://www.ncbi.nlm.nih.gov/entrez/eutils/efetch.fcgi?db=pubmed&retmode=xml&id=18632282

XML::Rules is sax (maybe both), and XML::Twig is definetly both.