- From: <bugzilla@wiggum.w3.org>
- Date: Wed, 29 Nov 2006 00:24:34 +0000
- To: public-qt-comments@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=4024 ------- Comment #6 from mrys@microsoft.com 2006-11-29 00:24 ------- There is a bit of "standard" history behind that behaviour. There is really no good semantic meaning for fn:boolean on heterogeneous sequences. E.g., fn:boolean((<a/>, false()))... should that be true, false? So some people wanted this to be an error (especially since it is also being used in the context of predicates as the implied semantics). Other people that have runtime semantics, did not want to evaluate 2000 values before hitting the heterogeneity and wanted a more performant semantics. So we decided, as a compromise, to make this a static error, but have efficient, dynamic semantics for the implementations, that do not do static analysis.
Received on Wednesday, 29 November 2006 00:24:42 UTC