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

[Bug 28041] New: [XSLT30] Maps have implementation defined order, but this is not specified as such

From: <bugzilla@jessica.w3.org>
Date: Tue, 17 Feb 2015 15:48:56 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-28041-523@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28041

            Bug ID: 28041
           Summary: [XSLT30] Maps have implementation defined order, but
                    this is not specified as such
           Product: XPath / XQuery / XSLT
           Version: Member-only Editors Drafts
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSLT 3.0
          Assignee: mike@saxonica.com
          Reporter: abel.online@xs4all.nl
        QA Contact: public-qt-comments@w3.org

Under map:keys we say that the order of the result is implementation defined.
Under maps (section 21.1 and 21.1.1) we do not say such a thing.

Furthermore, we do not clarify whether deep-equal(map:keys($m), map:keys($m))
is pairwise equal or not, but we do say that map:keys is deterministic (and the
definition of deterministic in XP30 is defined that it must be pairwise equal).

The function map:for-each-entry has the same ambiguity.

This bug equally applies to XSLT 3.0 LCWD and XPFO 3.1 CR.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 17 February 2015 15:49:04 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 17 February 2015 15:49:04 UTC