But in fact passing (1,2,3) as a parameter is quite likely to be of
great use in just such a scenario.
I think Saxon could easily be adapted to use such a scheme.
Yes, but I think the command line is getting pretty heavily overloaded. I
don't want to turn it into a programming language in its own right. People
can easily use tokenize() - or even saxon:evaluate() - once the parameter
value arrives in the XSLT space.
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>
--~--