W3C home > Mailing lists > Public > public-qt-comments@w3.org > September 2006

[Bug 3699] nodecomparisonerr-1

From: <bugzilla@wiggum.w3.org>
Date: Tue, 12 Sep 2006 06:49:12 +0000
CC:
To: public-qt-comments@w3.org
Message-Id: <E1GN252-0000EU-Gm@wiggum.w3.org>

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

           Summary: nodecomparisonerr-1
           Product: XML Query Test Suite
           Version: unspecified
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XML Query Test Suite
        AssignedTo: andrew.eisenberg@us.ibm.com
        ReportedBy: tim@cbcl.co.uk
         QAContact: public-qt-comments@w3.org


Although the test

fn:count(() is 100)

permits a type checking error, it also permits the result 0.

However, the rules for evaluating this state that:

1. The operands of a node comparison are evaluated in implementation-dependent
order.
2. Each operand must be either a single node or an empty sequence; otherwise a
type error is raised [err:XPTY0004].
3. If either operand is an empty sequence, the result of the comparison is an
empty sequence, and the implementation need not evaluate the other operand or
apply the operator. However, an implementation may choose to evaluate the other
operand in order to determine whether it raises an error.

My reading of this is that (2) ensure that an error is raised before reaching
stage (3).  If this is not the case, should the order of (2) and (3) not be
switched for clarity?
Received on Tuesday, 12 September 2006 06:49:33 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:14 UTC