- From: <bugzilla@jessica.w3.org>
- Date: Wed, 14 Mar 2012 17:48:33 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16370
Michael Kay <mike@saxonica.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mike@saxonica.com
--- Comment #1 from Michael Kay <mike@saxonica.com> 2012-03-14 17:48:32 UTC ---
I think the rule is that if type errors are raised statically then you can't
catch them.
I notice that XSLT 3.0 is not clear about whether xsl:try/xsl:catch catches
type errors. It only speaks of dynamic errors being caught.
We already have a lack of interoperability caused by allowing implementations
to decide whether to raise type errors statically or dynamically. I don't think
try/catch makes this significantly worse. Anyone who catches type errors and
tries to recover from them needs to know that this won't work on an
implementation that detects them statically.
--
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 Wednesday, 14 March 2012 17:48:35 UTC