in reply to XML Modules Comparisons

In both the case of XML::Simple and XML::Parser, these only deal with the input of XML into your program; you'd still need another module that deals with the output such as XML::AutoWriter; thus your input and output methods may seem very disjointed. While I've not used Xerces, it easy to see that it handles both sides of XML (parsing and generating). The only thing that is of concern is that it is a perl module that sits on top of a C/C++ library; thus, some of the function calling seems to get hairy, and there might be some performance penalties. Xerces appears to be very well documented by the Apache team (I've yet to see anything Apache puts out that's poorly documented), so you'll find just as much info about Xerces as you would with XML::Simple or ::Parser.

I'd say the best thing to do is to try to write some quick sample application code using both, and decide which one feels 'best' to work with, with all other factors being equal; consider expandibility, code maintainence, and how others may seem the code as part of your decision.


Dr. Michael K. Neylon - mneylon-pm@masemware.com || "You've left the lens cap of your mind on again, Pinky" - The Brain

Replies are listed 'Best First'.
Re: Re: XML Modules an
by clintp (Curate) on Jul 09, 2001 at 17:40 UTC
    Small correction: XML::Simple does have an output method (XMLout) that will take a perl structure and produce XML for it.
Re2: XML Modules comparison
by pmas (Hermit) on Jul 09, 2001 at 17:46 UTC
    Masem said it all.

    I will consider also to compare support for arr considered modules (mail lists, if any), try to post a question if any arises during pilot test, and compare response.

    If module has strong following, it is likely it will stay around for a while. SO if you invest time to develop any module, you want the module with staying power.

    pmas

    To make errors is human. But to make million errors per second, you need a computer.