- From: <bugzilla@jessica.w3.org>
- Date: Wed, 29 Jun 2016 11:21:32 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29713
Michael Kay <mike@saxonica.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|jim.melton@acm.org |jonathan.robie@gmail.com
CC| |mike@saxonica.com
Component|XQueryX 3.1 |XQuery 3.2 Use Cases and
| |Requirements
--- Comment #1 from Michael Kay <mike@saxonica.com> ---
Changing this to an XQuery 3.2 requirement, since we're long past accepting new
requirements for XQ 3.1, especially anything as fundamental as this.
It's something that would be very nice to have (along with
optional/defaultable) parameters), but it's not at all easy to achieve, given
that currently it's the combination of name+arity that uniquely identifies a
function, rather than the name alone.
The availability of maps and arrays in XQ 3.1 provides a workaround in terms of
allowing more flexible function interfaces; for example see the fn:transform
method in which all arguments are supplied as entries in a map.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 29 June 2016 11:21:40 UTC