Bytecode generation: xs:string returns "" instead of ()
The generated bytecode for an expression such as xs:string(/a/b/c) returns a zero length string instead of an empty sequence when the supplied node-set is empty.
The problem is present in 9.6 and earlier releases.
I have written a number of new W3C QT3 test cases for value comparisons; the problem is revealed by test case value-comp-eq-string-4
#2 Updated by Michael Kay over 5 years ago
Turns out the first patch solves the problem on the "compileToPrimitive" path but not on the "compileToItem" path in AnyTypeToStringConverterCompiler. The problem is revealed by the same test, run with option -unfolded. An additional patch is being applied to the same class.
Please register to edit this issue