Actions
Bug #2169
closed![Author: Michael Kay](https://www.gravatar.com/avatar/db6526d63053f09b62e52c2da8b2230a?rating=PG&size=50&default=https%3A%2F%2Fassets.plan.io%2Fimages%2Fdefault_avatar.png)
![Assignee: Michael Kay](https://www.gravatar.com/avatar/db6526d63053f09b62e52c2da8b2230a?rating=PG&size=22&default=https%3A%2F%2Fassets.plan.io%2Fimages%2Fdefault_avatar.png)
map{} is parsed as ExprSingle, not as a Primary
Start date:
2014-10-08
Due date:
% Done:
100%
Estimated time:
Legacy ID:
Applies to branch:
9.6
Fix Committed on Branch:
9.6
Fixed in Maintenance Release:
Platforms:
Description
The new syntax map{a "b"} is recognized as an ExprSingle, not as a Primary. This means it cannot be used in some contexts, for example
map{} instance of map(*)
Also, Saxon recognizes map expressions in the form {a (without the "map" keyword), which was a syntax at one time proposed by the W3C working groups, but subsequently dropped.
A patch is being committed on the 9.6 and 9.7 branches to recognize map expressions only as a Primary, and to drop support for the "bare curly braces" syntax, which can lead to confusing error messages.
Please register to edit this issue
Actions