Bug #6473
closed
Expression `/[x]` is not accepted
0%
Description
The expression /[x,y] is apparently legal in XPath 3.1 -- it should be interpreted as the path / (selecting the root node) followed by an array constructor evaluated with that root node as the context item. (One might imagine an alternative interpretation in which [x,y] is interpreted as a predicate filter, but that doesn't parse.)
Saxon rejects this expression with a syntax error.
The expression /map{a:2} also appears to be legal, and is also rejected by Saxon.
Related issues
Updated by Michael Kay 5 months ago
- Status changed from New to In Progress
- Applies to branch 11, 12, trunk added
- Platforms .NET, Java added
Test cases have been added to the QT4 test suite, test set prod-PathExpr.
Updated by Michael Kay 5 months ago
- Status changed from In Progress to Resolved
- Fix Committed on Branch 12, trunk added
Fixed on 12.x branch. Was already fixed on 13.x. Note that some of the new tests in prod-PathExpr for new XP40 features are not passed by Saxon 12.x, and we don't intend to change this (the spec is still moving).
Updated by Debbie Lockett 4 months ago
- Copied to Bug #6516: Expression `/[x]` is not accepted added
Please register to edit this issue
.