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

[Bug 22127] Allow xsl:next-match inside xsl:for-each

From: <bugzilla@jessica.w3.org>
Date: Tue, 21 May 2013 22:30:41 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-22127-523-mb24VsyRkF@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22127

--- Comment #1 from Michael Kay <mike@saxonica.com> ---
I'd like to see a compelling use case. 

My instincts are against adding more "current this" and "current that" values;
even if scoped statically to a template rule, they add semantic complexity. For
example, this facility would complicate the streamability rules. If we did
introduce a "current matched node" I think we would need an interrogative
function to return it. (In practice, I suspect this new function would then be
used a lot more than the proposed xsl:next-match facility...)

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 21 May 2013 22:30:46 UTC

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