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

[Bug 24511] New: Function item and maps, error situations or side effects

From: <bugzilla@jessica.w3.org>
Date: Wed, 05 Feb 2014 04:27:12 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-24511-523@http.www.w3.org/Bugs/Public/>

            Bug ID: 24511
           Summary: Function item and maps, error situations or side
           Product: XPath / XQuery / XSLT
           Version: Last Call drafts
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSLT 3.0
          Assignee: mike@saxonica.com
          Reporter: abel.braaksma@xs4all.nl
        QA Contact: public-qt-comments@w3.org

Given that a function with a signature function(xs:anyAtomicType) as item()*
matches any map, should we say anything about assigning functions to items that
are declared as maps?

I mean, one could assign concat#1 to a map, which wouldn't do much other than
return the key as the value. But what happens if a function returns an error,
i.e., error#1 (or is the "none" type of fn:error not compatible with item()*?).
But any other function can return an error.

And what happens when functions have side effects, like creating a new node or
a constructor function, or a function calling xsl:stream? 

Perhaps the behavior should be implementation defined, similarly to
xsl:variable (which can be evaluated again and again, but can also be cached).

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 5 February 2014 04:27:19 UTC

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