<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://www.w3.org/Bugs/Public/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.4"
          urlbase="https://www.w3.org/Bugs/Public/"
          
          maintainer="sysbot+bugzilla@w3.org"
>

    <bug>
          <bug_id>18356</bug_id>
          
          <creation_ts>2012-07-23 12:01:40 +0000</creation_ts>
          <short_desc>[XSLT 2.0] catching type errors</short_desc>
          <delta_ts>2013-02-16 12:38:43 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>XPath / XQuery / XSLT</product>
          <component>XSLT 3.0</component>
          <version>Working drafts</version>
          <rep_platform>PC</rep_platform>
          <op_sys>All</op_sys>
          <bug_status>CLOSED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>P2</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Michael Kay">mike</reporter>
          <assigned_to name="Michael Kay">mike</assigned_to>
          
          
          <qa_contact name="Mailing list for public feedback on specs from XSL and XML Query WGs">public-qt-comments</qa_contact>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>71304</commentid>
    <comment_count>0</comment_count>
    <who name="Michael Kay">mike</who>
    <bug_when>2012-07-23 12:01:40 +0000</bug_when>
    <thetext>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&apos;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.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>82911</commentid>
    <comment_count>1</comment_count>
    <who name="Michael Kay">mike</who>
    <bug_when>2013-02-11 16:09:05 +0000</bug_when>
    <thetext>Action on the editor to check whether this is consistent with what the spec currently says or if not, what changes are needed.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>83128</commentid>
    <comment_count>2</comment_count>
    <who name="Michael Kay">mike</who>
    <bug_when>2013-02-13 23:24:56 +0000</bug_when>
    <thetext>The rules for try/catch have been clarified to cover the points listed.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>83220</commentid>
    <comment_count>3</comment_count>
    <who name="Michael Kay">mike</who>
    <bug_when>2013-02-16 12:38:43 +0000</bug_when>
    <thetext>Changes applied in draft N.</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>