- From: <bugzilla@jessica.w3.org>
- Date: Mon, 07 Nov 2016 20:54:33 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29959 --- Comment #8 from Josh Spiegel <josh.spiegel@oracle.com> --- I see what you are referring to now: fn:transform "If the delivery format is saved, the value is the absolute URI of the location where the serialized result has been saved. The saved document will not be accessible at this location within the current ·execution scope· (this is to prevent any dependency on order of execution)." I wasn't aware of this until now and I am surprised to see this in the specification. Even if side effects aren't visible within an execution scope, this still doesn't work. In many cases, there is no guarantee as to how many times a function call will be evaluated. So, the behavior of this feature is not well-defined or interoperable. For example, processors may do lazy evaluation, rewrite multiple for clauses using a hash-join, detect errors at different points, lift let clauses outside of for clauses, and so on. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 7 November 2016 20:54:41 UTC