> Yes, that's what Embperl currently does. Additionaly it caches parsed XSLT
> stylesheets and XML documents (you can configure that), so when you make a
> lot of transformations using the same stylesheet on different doucments, the
> sytlesheet only get's parsed once (Embperl automaticly reparses
>
> Ahh, perhaps I am starting to get it. Basically the XSLT recipes
> configure the processing of the code to use XML libraries, and when you
> do an Execute on them, they make the calls using the specified XML
> library (libxml2 in my case). So all the XSLT functionality is done
> by the respe
> > It seems to me (from document fragments and example code) that the 'XML
> > integration' has mostly targetted the XSLT transformations.
> >
>
> It's maily intended for transforming it and generating output. For now this
> means mainly XSLT.
Ahh, perhaps I am starting to get it. Basically th
> It seems to me (from document fragments and example code) that the 'XML
> integration' has mostly targetted the XSLT transformations.
>
It's maily intended for transforming it and generating output. For now this
means mainly XSLT.
> What if I just want to parse some XML files?
>
> - are the
On 16-Apr-2002 Cameron McBride wrote:
> It seems to me (from document fragments and example code) that the 'XML
> integration' has mostly targetted the XSLT transformations.
>
> What if I just want to parse some XML files?
>
> - are the libxml2 documented functions just bootstrapped into the
