W3C home > Mailing lists > Public > public-qt-comments@w3.org > April 2013

[Bug 21666] New: [XQ30] try/catch expression with no matching catch clause

From: <bugzilla@jessica.w3.org>
Date: Thu, 11 Apr 2013 16:18:35 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-21666-523@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21666

            Bug ID: 21666
           Summary: [XQ30] try/catch expression with no matching catch
                    clause
    Classification: Unclassified
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          Hardware: PC
                OS: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XQuery 3.0
          Assignee: jonathan.robie@gmail.com
          Reporter: andrew.eisenberg@us.ibm.com
        QA Contact: public-qt-comments@w3.org

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."

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 11 April 2013 16:18:40 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:52 UTC