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

[Bug 29959] [xq31] fn:put()

From: <bugzilla@jessica.w3.org>
Date: Mon, 07 Nov 2016 14:43:06 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29959-523-XNrPNxGCc7@http.www.w3.org/Bugs/Public/>

--- Comment #3 from Josh Spiegel <josh.spiegel@oracle.com> ---

> This definition of fn:put() is actually broken in that it can be 
> optimized away, so it should also be marked impure - we used to 
> have a pragma for that I think? Or it should return a list of URIs.

I don't think it is broken.  fn:put() is an updating function and any
expression that calls it becomes an updating expression. 

I think the only problem is that we are normatively defining a feature in XQ
based on a Last Call Working Draft of XQUF.  

I don't know what you mean about using fn:transform (I am not very familiar
with XSLT).  Could you give an example?

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Monday, 7 November 2016 14:43:14 UTC

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