Bug 20451 - [F+O 3.0] Type errors vs dynamic errors
[F+O 3.0] Type errors vs dynamic errors
Status: RESOLVED FIXED
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Functions and Operators 3.0
Last Call drafts
PC All
: P2 minor
: ---
Assigned To: Michael Kay
Mailing list for public feedback on specs from XSL and XML Query WGs
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-12-19 17:43 UTC by Michael Kay
Modified: 2012-12-20 10:05 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Kay 2012-12-19 17:43:30 UTC
The F+O specification is not always clear about which errors are type errors and which errors are dynamic errors. The distinction affects whether the error can be raised statically, and whether it can be caught using try/catch.
Comment 1 Michael Kay 2012-12-20 10:05:40 UTC
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).