This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
In the resolution of Bug 29185, XQuery 3.1 has changed {Expr} to {Expr?} at various points in the grammar. So a few tests that were illegal in older versions are legal in XQuery 3.1. Consequently, the following tests should be split into 3.1 and pre-3.1 versions, with different expectations: prod/CompCommentConstructor.xml#K2-ComputeConComment-4 prod/CompTextConstructor.xml#K2-ConText-5 prod/UnorderedExpr.xml#K-OrderExpr-1 prod/UnorderedExpr.xml#K-OrderExpr-2 misc/CombinedErrorCodes.xml#K-CombinedErrorCodes-13 misc/CombinedErrorCodes.xml#K-CombinedErrorCodes-14 misc/CombinedErrorCodes.xml#K-CombinedErrorCodes-15
Also this one: prod/DirElemContent.xml#K2-DirectConElemContent-26
(In reply to Josh Spiegel from comment #1) > Also this one: > prod/DirElemContent.xml#K2-DirectConElemContent-26 No, K2-DirectConElemContent-26 is only for XQ10 and XQ30. The XQ31+ version is K2-DirectConElemContent-26a
Yes, you are right. I was looking at the github mirror (https://github.com/LeoWoerteler/QT3TS) which appears to have stopped updating back in October. This test was fixed recently.
(In reply to Josh Spiegel from comment #3) > Yes, you are right. I was looking at the github mirror > (https://github.com/LeoWoerteler/QT3TS) which appears to have stopped > updating back in October. Thanks for the reminder. Since today, the mirror is updated again.
Thanks! I have found it very useful when searching for tests and looking at change history.
I have added new test case which are variants of the ones suggested in comment #0. Committed to cvs
I have corrected the expected results of prod/CompCommentConstructor.xml#K2-ComputeConComment-4 (It should produce a comment with zero-length content. For some reason text{} produces an empty sequence but comment{} produces a zero-length comment node.)