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

[Bug 29346] [XP31] XPath-style currying, or the arrow operator, may require a bit more specification

From: <bugzilla@jessica.w3.org>
Date: Fri, 18 Dec 2015 12:29:02 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29346-523-31FtYoz0Or@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29346

--- Comment #6 from Michael Kay <mike@saxonica.com> ---
>What is your take on aligning this more closely with the static function call
syntax, i.e. my point (6) in comment#0? That is, allowing a => concat#3('b',
'c')? It requires adding NamedFunctionRef with otherwise the same semantics as
you describe for EQName.

We need a very strong justification to change the grammar at this stage, and I
can't see that this is important enough. It only provides cosmetic improvements
for something that is surely not a common requirement.

Incidentally, as defined in the spec concat#3(1,2,3) is not a static function
call, it is a dynamic function call.

If we want more orthogonality in the grammar then the top thing on my list
would be to add VarRef on the rhs of a lookup operator. But we don't want minor
improvements now, we want to finish.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 18 December 2015 12:29:06 UTC

This archive was generated by hypermail 2.3.1 : Friday, 18 December 2015 12:29:06 UTC