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

[Bug 20981] Why accumulators are not passed to xsl:evaluate?

From: <bugzilla@jessica.w3.org>
Date: Thu, 14 Feb 2013 23:23:35 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-20981-523-yRJkTxjXj0@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20981

--- Comment #1 from Michael Kay <mike@saxonica.com> ---
I think the rules may be over-restrictive.

In the absence of streaming on the accumulator, the only reason to have
restrictions is the possibility of circularity (and dependence on order of
evaluation) among multiple accumulators. But I don't think this is in principle
different from allowing infinite recursion in ordinary function or template
calls. So with an accumulator that specifies streamable="no" we should lift
restrictions.

With streaming on, an alternative design might be to say that if an accumulator
function is called and the context node is not the current node in a streamed
input document, then calling the accumulator function is allowed, but fails
dynamically. This might lead to a simpler set of rules.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 14 February 2013 23:23:38 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 14 February 2013 23:23:38 GMT