[Bioperl-l] XML parser preference?

Chris Fields cjfields at uiuc.edu
Wed Aug 9 19:21:39 EDT 2006


Brian, 

The main reason I chose XML::Simple is that I wanted something
up-and-running ASAP; the chunks of XML normally are small and not too
complex, but for esearch/elink they can be quite long).  The problem I
foresee is we currently have prereq's for the following XML parsers:

XML::SAX
XML::Parser
XML::DOM
XML::Twig

which various modules use (this doesn't include the XML writers, either).  

I didn't think it was a good idea to lump yet another prereq on top of
those.  Anyway, I can always replace the backend XML parser along the way as
long as the front-end API is the same.  Which reminds me, I need to work on
that...

Chris

> -----Original Message-----
> From: bioperl-l-bounces at lists.open-bio.org [mailto:bioperl-l-
> bounces at lists.open-bio.org] On Behalf Of Brian Osborne
> Sent: Wednesday, August 09, 2006 6:05 PM
> To: Chris Fields; bioperl-l at lists.open-bio.org
> Subject: Re: [Bioperl-l] XML parser preference?
> 
> Chris,
> 
> I don't think there's any reason not to use XML::Simple if it's guaranteed
> that the chunks of XML are small.
> 
> Brian O.
> 
> 
> On 8/9/06 5:47 PM, "Chris Fields" <cjfields at uiuc.edu> wrote:
> 
> > I am finishing up the EUtilities modules in bioperl-live.  I'm using
> > XML::Simple to grab the IDs and other information from XML returned from
> > NCBI via esearch/elink/epost queries, but I noticed that no other
> Bioperl
> > modules use this particular module.
> 
> 
> _______________________________________________
> Bioperl-l mailing list
> Bioperl-l at lists.open-bio.org
> http://lists.open-bio.org/mailman/listinfo/bioperl-l



More information about the Bioperl-l mailing list