in reply to Re: Picking an XML Module
in thread Picking an XML Module
The main limitation of XML::Parser is that it is a low level module: you have to do a lot of work yourself. The best example is probably that you have to buffer the data returned by the character handler, or it will come in several chunks. In general SAX-level handlers are quite a pain to write. And XML::Parser is not even SAX, so you don't get to benefit from the work that is being done at the moment on SAX modules (XML::SAX::Machines or XML::Filter::Dispatcher for example have some very good ideas). OTOH I must sau that antiquated as it is, XML::PArser's interface is a bit more convenient that pure SAX.
But if I compare this to the simplicity of... XML::Simple (which would not work in this case, it does not deal well with mixed content), or to the power of XML::LibXML's XPath engine, I don't think that XML::Parser is a good choice today.
There are also some problems with the way XML::Parser deals with entities (especially in attribute values) that can be annoying if your XML uses them.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re: Re: Re: Picking an XML Module
by vek (Prior) on Aug 03, 2003 at 19:01 UTC |