W3C home > Mailing lists > Public > public-qt-comments@w3.org > July 2012

[Bug 18356] New: [XSLT 2.0] catching type errors

From: <bugzilla@jessica.w3.org>
Date: Mon, 23 Jul 2012 12:01:40 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-18356-523@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18356

           Summary: [XSLT 2.0] catching type errors
           Product: XPath / XQuery / XSLT
           Version: Working drafts
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSLT 3.0
        AssignedTo: mike@saxonica.com
        ReportedBy: mike@saxonica.com
         QAContact: public-qt-comments@w3.org


ACTION A-515-03 on Michael Kay to raise a bug against XSLT to bring it in line
with the decision made in bug
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16370 (Does a TryCatch
expression catch a type error raised during the static analysis phase?) 

Effects include:

(a) try/catch can catch type errors if they are not detected statically

(b) a try/catch around the body of a function does NOT catch the type error
that occurs if the body of the function delivers the wrong type of result. This
can be caught only by putting a try/catch around the function call.

(c) equally, a try/catch in the initializer of a variable will not catch the
error when the initializer's result does not match the variable declaration. In
the case of a global variable this error cannot be caught, because there is
nowhere to catch it.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Monday, 23 July 2012 12:01:46 UTC

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