"Claudio Russo" <crusso(_at_)azurixbasa(_dot_)com(_dot_)ar> wrote in message
news:C795D31002324444B1D95D8940C8A78F0BECA4(_at_)azarlap1exh01(_dot_)azxnet(_dot_)azurixbasa(_dot_)com(_dot_)ar(_dot_)(_dot_)(_dot_)
Dimitre,
So, this library, somehow replaces any/some/all of the extensions provided
by MSXML, XALAN, SAXON, and other interpreters?
FXSL doesn't replace anything -- it just fills an existing gap in the
traditional ways of applying XSLT. This gap is called higher order functions
and/or functional programming.
Probably if HOF were part of the language from the very start there would
have been much less extension functions developed, but this is not how XSLT
evolved. The ideas lying behind FXSL are still considered heretic by some
people.
Meaning that is pure XSLT 2.0, the interpreters that stack to XSLT 1.0
wouldn't be capable of run them?
Until recently it was on the contrary -- it was possible to "run FXSL" only
on XSLT 1.0. Then I adapted it (with some very few and minot changes) so
that it produced the correct results in XSLT 2.0.
=====
Cheers,
Dimitre Novatchev.
http://fxsl.sourceforge.net/ -- the home of FXSL
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list