Of course, the same solution can be re-written for XSLT 1.0.
FXSL for XSLT 1.0 also has a "scanl" and "map" templates.
Currying will have to be used explicitly.
The code will be a bit longer but it will implement the same algorithm.
As the time has come for everyone to consider moving to XSLT 2.0, I
have stopped actively developing FXSL 1.x since almost two years ago.
FXSL 2.0 has undergone extensive development and I would recommend
using XSLT 2.0 + FXSL 2.0.
--
Cheers,
Dimitre Novatchev
---------------------------------------
Truly great madness cannot be achieved without significant intelligence.
On 7/12/06, Steve <subsume(_at_)gmail(_dot_)com> wrote:
Very interesting. Do you think this will work with XSL 1.0?
My parser (MSXML) doesn' support 2.0, but I do have FXSL.
-Steve
On 7/12/06, Dimitre Novatchev <dnovatchev(_at_)gmail(_dot_)com> wrote:
> Here's one possible solution:
>
> This transformation:
>
> <xsl:stylesheet version="2.0"
> xmlns:xsl="http://www.w3.org/1999/XSL/Transform";
> xmlns:xs="http://www.w3.org/2001/XMLSchema";
> xmlns:f="http://fxsl.sf.net/";
> exclude-result-prefixes="f xs"
--~------------------------------------------------------------------
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>
--~--