|
|
 next
|
  Subject: Path evaluation bug (?) concerning constructors
Author: Hans-Juergen Rennau
Date: 04 Sep 2007 04:13 AM
|
Hello, hello,
if I am not mistaken, there is a bug in the built-in processor, concerning the evaluation of path expressions. If the first step evaluates to the empty sequence and the second step is a constructor, the constructor is evaluated, although it shouldn't be.
Trying out other expressions for the second step - e.g. evaluating to an element node or a literal - the evaluation is correct: the whole path evaluates to the empty sequence.
Trying out other processors (Saxon, DataDirect), the evaluation is correct.
In this example, $sw_withAtt_ty evaluates to the empty sequence, and $cfg evaluates to a node. These expressions
...
$sw_withAtt_ty/attribute yogiAtt {},
$sw_withAtt_ty/<yogiElem/>,
$sw_withAtt_ty/element {"yogiElem2"} {},
$sw_withAtt_ty/$cfg,
$sw_withAtt_ty/"yogiLiteral",
...
produce three yogi's, but no copy of $cfg, nor the literal.
With kind regards -
Hans-Juergen Rennau
|
|
|
|
top