[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: Equal rights for xsl:next-match & co
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).
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|