Subject: RE: [xsl] info on sablotron? From: "bryan" <bry@xxxxxxxxxx> Date: Mon, 9 Sep 2002 12:00:35 +0200 |
Petr wrote: >The current version (v0.96) is supposed to be XSLT 1.0 compliant. Its >performance is comparable to other C/C++ engines (libxslt is about 50% >faster). Thanks, that's great. >node-set() >isn't supported yet. > node-sets can be passed to XSLT as external objects. Do you mean that a node-set can be passed and accessed without using a node-set function? That would be a contradiction of what you said above vis-à-vis compliance. Do you mean that the exslt node-set() is not supported but sablotron does have a way for working with node-sets? Or do you mean that if a node-set is passed as an external object to the xslt then the xslt can access said node-set without an extension function, otherwise the xslt cannot access the node-set; I know this sounds sort of weird but it's how things work in .Net when dealing with external node-sets being passed in, when they're passed in you can't access them with node-set() but just access them without an extension function, and when you build up a node-set internal to your document you need to use node-set() - so anyway that's the reason I ask what otherwise seems like a weird question. Or is the "node-sets can be passed to XSLT as external objects" in reference to "virtual xml documents" as per the xml.com article on the same subject in Sablotron? Sorry to be a bother but I want to understand it quickly as my application structures are very node-set dependant. XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] info on sablotron?, Petr Cimprich | Thread | Re: [xsl] info on sablotron?, Petr Cimprich |
Re: [xsl] CDATA section, Peter Davis | Date | RE: [xsl] CDATA section, Michael Kay |
Month |