Also, is there any real advantage to specifying as="element()" other
then readability/documentation? You've recently discussed the
advantages of doing this for non-element data types (e.g. numeric
functions). Are there similar advantages for element()?
Thanks,
~Chris
Christopher Scott
Loan Fulfillment Solutions
Fiserv
-----Original Message-----
From: Michael Kay [mailto:mike(_at_)saxonica(_dot_)com]
Sent: Monday, March 02, 2009 10:52 AM
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Subject: RE: [xsl] Push Processing
Michael Kay wrote:
<xsl:function name="f:expand" as="element()">
<xsl:param name="item" as="element(item)"/>
<xsl:param name="child" as="element()?"/>
<xsl:choose>
<xsl:when test="exists($child)">
<xsl:sequence select="$child"/>
</xsl:when>
<xsl:otherwise>
<emptyCell/>
</xsl:otherwise>
</xsl:choose>
</xsl:function>
Just out of interest, why do you pass the $item param here?
Because I changed the design half way through.
Michael Kay
http://www.saxonica.com/
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--