On Wednesday 20 February 2002 10:11, Steve Willer wrote: > On Wed, 20 Feb 2002, Matt Sergeant wrote: > > I think this is a bug in XML::LibXML that Christian Glahn is working on. > > I'll keep the list informed as to when it's fixed. I'm also going to > > investigate migrating XML::LibXML to XML::GDOME within AxKit. > > I saw the announcement for this new module and its XSL sibling. But I must > admit, I was wondering "what's in it for me?" I guess the libgdome library > exposes a DOM2 interface, and the XML::GDOME module follows suit. It > doesn't seem like a big plus, but perhaps I'm ignorant about this. > > Could you tell me what the plus side is in moving over to it?
It would be a really BIG advantage to be able to parse XML using a C library, then manipulate the resulting DOM in perl, thats the big deal. That would also allow you to do things like cache DOM trees in memory and pass them around. You can SORT OF do that now, but to perl they are just big chunks of unintelligible data. Sounds like GDOME will give programmers a lot more flexibility in writing XML processors in perl. Previously if you wanted to things like this you had to use a parser written in perl (SLOWWWWWW). > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
