W3C home > Mailing lists > Public > public-qt-comments@w3.org > May 2015

[Bug 28699] New: Editorial: Unary lookup examples assume arrays without saying so

From: <bugzilla@jessica.w3.org>
Date: Tue, 26 May 2015 15:02:26 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-28699-523@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28699

            Bug ID: 28699
           Summary: Editorial: Unary lookup examples assume arrays without
                    saying so
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XQuery 3.1
          Assignee: jonathan.robie@gmail.com
          Reporter: pwalmsley@datypic.com
        QA Contact: public-qt-comments@w3.org

In the examples of the Unary operator, it says:


   let $x:= <node i="3"/> return ?($x/@i) does not raise a type error because
the attribute is untyped.

   But let $x:= <node i="3"/> return ?($x/@i+1) does raise a type error because
the + operator with an untyped operand returns a double.


This would only be true if the context item is an array, right?  It seems it
could be appropriate for a map. 


Likewise for the example that says:

   ?(3.5) raises a type error because the parameter must be an integer.

Perhaps it should say:

   ?(3.5) raises a type error if the context item is an array because the
parameter must be an integer.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 26 May 2015 15:02:28 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 26 May 2015 15:02:29 UTC