[Bug 26788] [XPath30] XQuery-only errors in XPath 3.0 specification, like XQST0134

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26788

Michael Kay <mike@saxonica.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mike@saxonica.com

--- Comment #13 from Michael Kay <mike@saxonica.com> ---
One reason we felt able to change codes when moving things like format-date
from XSLT 2.0 to XPath 3.0 is that XSLT 2.0 had made error codes very "low
key", emphasizing that (a) conformant processors were not expected to generate
the error codes, and (b) there was no interface in the spec that allowed
applications access to them. 

These error codes are used to label error conditions in this specification...
They are provided primarily for ease of reference. Implementations may use
these codes when signaling errors, but they are not required to do so.

That changes with 3.0 and try/catch.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Thursday, 2 October 2014 14:37:31 UTC