Re: [xsl] Equal rights for xsl:next-match & co

[Evan Lenz <evan@xxxxxxxxxxxx>]

Right, I believe my expectation was that it would run the next-match 
based on the node that was matched (which may not be the current node if 
inside xsl:for-each). I don't believe it would make sense to say 
"next-match" on any other node, because there would no longer be any 
comparison by which a match could be said to be "next". Call it the 
"currently matched node" if necessary.

This would allow, for example:

<xsl:for-each select="1 to 10">
  <xsl:next-match/>
</xsl:for-each>

Evan

On 5/18/2013 1:51 AM, David Carlisle wrote:
> On 17/05/2013 20:29, Evan Lenz wrote:
> > What bugs me is that you can't call <xsl:next-match/> inside
> > <xsl:for-each> (because the "current template rule" is considered to
> > be nullified).
>
>
> I'm sure something could be defined but the semantics of that would be a
> little odd (whichever way it was defined) as next-match would need to
> trigger a template matching the node that matched the current template
> but that would not (usually) be the current node within a for-each.
>
>
> David