Since I am more used to xalan, I guess it is a bit more (much too?) flexible
with this. Maybe it is a bug actually.
If it allows variables here it's a bug, the language does not allow
flexibility here.
Nevertheless, the solution in my previous mail seems to make more
sense for me
The restriction on using variables in match patterns is a fairly
arbitrary restriction that serves no real purpose, but it isn't really up
to implementations not to enforce language rules just because they don't
make sense.
XSLT2 will drop this restriction and allow variables to be used.
David
________________________________________________________________________
This e-mail has been scanned for all viruses by Star. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________
--~------------------------------------------------------------------
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>
--~--