[Bug 1826] Editorial: op:union/op:intersect defined in F&O, but error handling in XPath 2.0

http://www.w3.org/Bugs/Public/show_bug.cgi?id=1826





------- Additional Comments From mike@saxonica.com  2005-07-28 17:52 -------
You're not the only one that's confused by the way the operator specifications
are split between the language book and the F+O book, but there is some method
in the madness: in general operators are polymorphic, and the language book
describes the logic that decides which of the various (non-polymorphic)
functions needs to be despatched. In this case there is no suitable function to
handle non-node-operands, so a type error is raised during the despatch process,
not by the function itself.

Michael Kay (personal response)

Received on Thursday, 28 July 2005 17:53:12 UTC