W3C home > Mailing lists > Public > public-qt-comments@w3.org > July 2014

[Bug 26324] XQuery 3.0's PostfixExpr is not properly represented in XQueryX 3.0

From: <bugzilla@jessica.w3.org>
Date: Sun, 13 Jul 2014 23:31:31 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-26324-523-59n3o2sIy6@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26324

Jim Melton <jim.melton@acm.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |INVALID

--- Comment #1 from Jim Melton <jim.melton@acm.org> ---
Upon additional consideration, especially after re-reading XQuery 3.0, section
3.2 "Postfix Expressions", last paragraph:

   An expression (other than a raw EQName) followed by an argument list in
parentheses (that is, E1(E2, E3, ...)) is referred to as a dynamic function
call. Its effect is to evaluate E1 to obtain a function, and then call that
function, with E2, E3, ... as arguments. Dynamic function calls are described
in 3.2.2 Dynamic Function Call.

I have concluded that the specific case of 12(1,2) is a useless artifact of
allowing far more useful expressions such as $x(1,2) (which is a
DynamicFunctionInvocation). 

The cost in "fixing" the case of 12(1,2) to be a (useless) Postfix Expression
instead of a Dynamic Function Invocation is in no way worth the effort,
particularly as it doesn't actually change any results. 

I am therefore marking this bug RESOLVED/INVALID and then marking it CLOSED. 

Sorry for the interruption.  Please carry on.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Sunday, 13 July 2014 23:31:32 UTC

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