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

[Bug 10716] New: [XPath21] Use of term "evaluation order" in XPath/XQuery

From: <bugzilla@jessica.w3.org>
Date: Fri, 24 Sep 2010 11:20:54 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-10716-523@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10716

           Summary: [XPath21] Use of term "evaluation order" in
                    XPath/XQuery
           Product: XPath / XQuery / XSLT
           Version: Member-only Editors Drafts
          Platform: PC
        OS/Version: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XPath 2.1
        AssignedTo: jonathan.robie@redhat.com
        ReportedBy: oliver@cbcl.co.uk
         QAContact: public-qt-comments@w3.org


This also applies to XQuery 1.1

Section 3.1.3 (of both specs) states:

Parentheses may be used to enforce a particular evaluation order in expressions
that contain multiple operators.

This is the only place in these specifications where the term "evaluation
order" is used. 

The use of the term here is different to the use of the term in Scripting
Extensions (as the evaluation order is entirely undefined).

It might be better to say:

Parentheses may be used to change how expressions are composed

or

Parentheses may be used to override the precedence rules


The following example is not really covered by "evaluation order":

for $x in 1 to 10 return $x, 1
for $x in 1 to 10 return ($x, 1)

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Friday, 24 September 2010 11:20:56 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 March 2012 18:15:06 GMT