- From: <bugzilla@jessica.w3.org>
- Date: Thu, 20 Aug 2015 17:23:14 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28955 --- Comment #1 from Abel Braaksma <abel.braaksma@xs4all.nl> --- This bug applies to section 8.3 on Try/Catch, the text: <quote> 1. All dynamic errors occurring during the evaluation of the xsl:try sequence constructor or select expression are caught (provided they match one of the xsl:catch elements). * This includes errors occurring in functions or templates invoked in the course of this evaluation, unless already caught by a nested xsl:try. * It also includes errors caused by calling the error function, or the xsl:message instruction with terminate="yes", or the xsl:assert instruction. * It does not include errors that occur while evaluating references to variables whose declaration and initialization is outside the xsl:try. </quote> The text seems to try to be complete, which is why I raised this bug. We could (should?) include that _using_ a variable that is declared as xs:error, and/or set to the value xs:error(), when used (not when declared) will raise an exception that _can_ be caught by the try/catch. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 20 August 2015 17:23:16 UTC