This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 21666 - [XQ30] try/catch expression with no matching catch clause
Summary: [XQ30] try/catch expression with no matching catch clause
Status: RESOLVED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XQuery 3.0 (show other bugs)
Version: Candidate Recommendation
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Jonathan Robie
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-11 16:18 UTC by Andrew Eisenberg
Modified: 2013-05-14 16:48 UTC (History)
0 users

See Also:


Attachments

Description Andrew Eisenberg 2013-04-11 16:18:35 UTC
The second paragraph in 3.15 Try/Catch Expressions says:

"If the target expression does not raise a dynamic error or a type error, the result of the try/catch expression is the result of the target expression."

The third paragraph says:

"If the target expression raises a dynamic error or a type error, the result of the try/catch expression is obtained by evaluating the first catch clause that "matches" the error value, as described below."

We do not cover the case where no catch clause matches the error value.

We might want to add the following sentence to the end of the third paragraph:

"If no catch clause "matches" the error value, then the try/catch expression raises the error that was raised by the target expression."
Comment 1 Jonathan Robie 2013-05-14 16:48:27 UTC
The WG agrees. I will add this.