This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: Designs for XSLT functions
- To: "'Jeni Tennison'" <mail at jenitennison dot com>
- Subject: [xsl] RE: Designs for XSLT functions
- From: "Michael Kay" <mhkay at iclway dot co dot uk>
- Date: Tue, 20 Feb 2001 15:59:08 -0000
- Cc: <xsl-list at lists dot mulberrytech dot com>
- Reply-To: xsl-list at lists dot mulberrytech dot com
> > Saxon allows xsl:for-each with saxon:function, but doesn't allow
> > saxon:return within xsl:for-each.
>
> Did you see the use cases that I put forward where it could be
> useful?:
>
> What do you think?
>
There's some logic to it: it suggests that <xsl:break> within an ordinary
<xsl:for-each> could also be defined cleanly, as "discard any result nodes
generated beyond this point". Could be useful:
<xsl:template match="h1">
<section>
<xsl:for-each select="following-sibling::*">
<xsl:if test="h1"><xsl:break/></xsl:if>
<xsl:apply-templates/>
</xsl:for-each>
</section>
</xsl:template>
An alternative to saxon:leading(). I quite like it. I wouldn't like it if
you could achieve this effect by writing a function and not achieve the same
effect inline.
Mike Kay
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list