W3C home > Mailing lists > Public > public-qt-comments@w3.org > November 2016

[Bug 30024] New: [F+O 3.1] Is map:entry superfluous?

From: <bugzilla@jessica.w3.org>
Date: Wed, 30 Nov 2016 17:08:45 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-30024-523@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=30024

            Bug ID: 30024
           Summary: [F+O 3.1] Is map:entry superfluous?
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Functions and Operators 3.1
          Assignee: mike@saxonica.com
          Reporter: mike@saxonica.com
        QA Contact: public-qt-comments@w3.org
  Target Milestone: ---

Comment from Thomas Fischer on public-qt-comments:

Hi,
the documentation for map:entry says:

Unlike the map expression (map{...}), this technique can be used to construct a
map with a variable number of entries, for example:
    map:merge(for $b in //book return map:entry($b/isbn, $b))

At least with Saxon-HE 9.7.0.8J you can achieve the same result with a simple
map constructor
    map:merge(for $b in //book return map{$b/isbn: $b})

I wonder, if this is just a "special feature" of Saxon or if there is any other
reason to keep map:entry in the proposal

salute
Th. Fischer

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 30 November 2016 17:08:53 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:58:03 UTC