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

[Bug 20451] [F+O 3.0] Type errors vs dynamic errors

From: <bugzilla@jessica.w3.org>
Date: Thu, 20 Dec 2012 10:05:40 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-20451-523-ziBQepHxaI@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20451

Michael Kay <mike@saxonica.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED
           Severity|normal                      |minor

--- Comment #1 from Michael Kay <mike@saxonica.com> ---
I have taken the liberty of treating this as editorial, and have classified all
ambiguous references to errors as either dynamic errors or type errors as
appropriate. 

In the case of FONS0004 I have changed this from a static error to a dynamic
error. (It was previously static because casting from string to QName required
the input to be a string literal; we already have a rule that allows such an
error to be raised statically if detected statically).

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 20 December 2012 10:05:46 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 20 December 2012 10:05:46 GMT