This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: max value
- From: "Charly" <cohana at investacorp dot com>
- To: <xsl-list at lists dot mulberrytech dot com>
- Date: Wed, 12 Dec 2001 09:43:21 -0800
- Subject: Re: [xsl] max value
- References: <200112120204.fBC24h455906@skew.org>
- Reply-to: xsl-list at lists dot mulberrytech dot com
Thanks Mike,
You were right I was working with a Beta version of XSLT processor .
----- Original Message -----
From: "Mike Brown" <mike@skew.org>
To: <xsl-list@lists.mulberrytech.com>
Sent: Tuesday, December 11, 2001 6:04 PM
Subject: Re: [xsl] max value
> Charly wrote:
> > Thanks Mark,
> > I still have a problem with the last(), after I do the sort the last
doesn't
> > give the last position anymore .
>
> position() and last() should be giving you the info relative to the
> sorted set. In the example you're going with, the last node should be
> the one with the max value. If it is not, then your XSLT processor is
> in violation of http://www.w3.org/TR/xslt#sorting which says
>
> "When a template is instantiated by xsl:apply-templates and
> xsl:for-each, the current node list list consists of the complete
> list of nodes being processed in sorted order."
>
> ...and http://www.w3.org/TR/xslt#section-Expressions explains that the
> current node list determines the context as used by the XPath functions
> such as last().
>
> - Mike
>
____________________________________________________________________________
> mike j. brown, fourthought.com | xml/xslt: http://skew.org/xml/
> denver/boulder, colorado, usa | personal: http://hyperreal.org/~mike/
>
> XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
>
>
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list