Actions
Support #1832
closed
op:is-same-node() fails to throw error when empty sequence passed as parameter
Status:
Closed
Priority:
Low
Assignee:
-
Category:
User error
Sprint/Milestone:
-
Start date:
2013-06-25
Due date:
% Done:
0%
Estimated time:
Legacy ID:
Applies to branch:
Fix Committed on Branch:
Fixed in Maintenance Release:
Platforms:
Description
In Saxon-PE 9.4.0.4, when I evaluate the XPath expression @/* is /..@, I get an empty sequence.
According to the XPath 2.0 spec at http://www.w3.org/TR/xpath-functions/#func-is-same-node,
a) Each of op:is-same-node()'s arguments (operands) must be a single node. If one of them is a sequence of more than one node, an error is thrown (Saxon does this correctly). However, when one of them is an empty sequence, Saxon should throw an error but doesn't.
b) op:is-same-node() is supposed to return a value of type xs:bool (if it returns at all). In the case of @/* is /..@, it returns an empty sequence.
Files
Please register to edit this issue
Actions
.