Re: best xml parser to use

My general decision tree goes sorta like this (non-XML parts removed):

 /----------\           +-----------+
< Parse XML? >  --NO>-- | (removed) |
 \----------/           +-----------+
      |
     YES
      V
      |
+---------------+
| Use XML::Twig |
+---------------+
[download]

Hopefully this decision tree helps you decide what is best.

;-)

Comment on Re: best xml parser to use Download Code

Replies are listed 'Best First'.

Re^2: best xml parser to use
by ftumsh (Scribe) on Jul 06, 2006 at 19:03 UTC

I appear to have only got xml::libxml::sax, is this good enough? the pod mention it might not be any good for production use. What others could I use?

[reply]

Re^3: best xml parser to use

by rvosa (Curate) on Jul 07, 2006 at 03:33 UTC

XML::Twig

[reply]

Re^4: best xml parser to use

by ftumsh (Scribe) on Jul 10, 2006 at 12:31 UTC

XML Twig saves on memory by only reading in bits of the xml. To know what bits you are interested in you have to tell it. As I don't know what tags will be used for a given document I can't do that so it would load the entire xml into memory which negates the point of Twig.

[reply]

Re^2: best xml parser to use
by Jenda (Abbot) on Aug 14, 2006 at 17:19 UTC

if ($xml->is_simple() and $xml->is_table_like()) {
  use XML::RAX;

} elsif (size($xml) < too_big()) {
  use XML::Simple;

} else {
  use XML::Twig;
  ...
  my $Data = $DataObj->simplify(forcearray => [...], keyattr =>{ ... }
+, group_tags => {...});
}
[download]

Update 2007-2-6: Tastes change. While I would probably still use XML::RAX for some tasks with table-like XML and XML::Simple for very simple XMLs, I'd most probably use my XML::Rules now. May look a bit twisted at first, but it's convenient and powerfull. IMHO of course ;-)

Jenda
Support Denmark!
Defend the free world!

[reply]
[d/l]