- From: <bugzilla@jessica.w3.org>
- Date: Wed, 02 Dec 2015 15:08:49 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29320 Bug ID: 29320 Summary: [XQ31] Switch expressions should have same error semantics as typeswitch Product: XPath / XQuery / XSLT Version: Candidate Recommendation Hardware: PC OS: All Status: NEW Severity: normal Priority: P2 Component: XQuery 3.1 Assignee: jonathan.robie@gmail.com Reporter: mike@saxonica.com QA Contact: public-qt-comments@w3.org Target Milestone: --- In section 2.3.4, conditional expressions and typeswitch expressions are given special status with regard to error handling: they "must not raise a dynamic error in respect of subexpressions occurring in a branch that is not selected, and must not return the value delivered by a branch unless that branch is selected". Section 3.15 on Switch Expressions states that switch expressions also have this protection: "Switch expressions have rules regarding the propagation of dynamic errors that take precedence over the general rules given in 2.3.4 Errors and Optimization. The return clauses of a switch expression must not raise any dynamic errors except in the effective case. Since 2.3.4 explicitly mentions conditional and typeswitch expressions as having this property, it should also mention switch expressions in the same sentence. Incidentally, I have no idea what the clause "and must not return the value delivered by a branch unless that branch is selected" is supposed to add. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Wednesday, 2 December 2015 15:09:10 UTC