Subject: [xsl] RE: Saxon versus Xalan implementations of evaluate() extension function? From: "Andrzej Taramina" <andrzej@xxxxxxxxxxx> Date: Thu, 7 Jul 2005 17:04:52 -0400 |
Michael: > Saxon 8.x does too much optimization to be able to guarantee that variables > declared in the stylesheet actually exist as such at run-time (for example, > variables that are never referenced are ignored completely). So I decided to > disallow direct access to variables in saxon:evaluate(). Instead, you can > pass parameters $p1..p9 to the query, e.g. > > saxon:evaluate("$p1 + 3", $x) > > returns 5 if $x is initialized to 2. Will it work if you do something like this: saxon:evaluate("$p1/node1/node2", $x) where $x is a node set? ie. Will it look for node1/node2 in the node set contained in $x? Thanks! ....Andrzej Chaeron Corporation http://www.chaeron.com
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
[xsl] RE: Saxon versus Xalan implem, Michael Kay | Thread | RE: [xsl] RE: Saxon versus Xalan im, Michael Kay |
Re: FW: [xsl]Add comment from xml s, Jon Gorman | Date | [xsl] multiple paths in the "use" i, Christian CXR Rasmus |
Month |