Having not even an infinitesimal amount of the mathematical
understanding that Dimitre has, I for myself am sure that I will never
be able to achieve exactly the same thing.
Note dimitre makes his code is availabel so you can use FXSL's
Xpath-parser-implemented-in-xslt without understanding how it works in
detail just as you can use Michael's xpath-parser-implemented-in-java
without understanding the underlying java code. (having never looked at
saxon's xpath parser sources I can definitely say that I have used that
quite often without understanding its implementation:-)
Is this comparable to what David proposed?
without a sample input or intended output the code posted went beyond
the threshold of what I can comprehend "by eye" but I suspect it's
rather different. What I was proposing didn't involve parsing any
user-supplied xpaths at all, just simply copying them from a
user-supplied config file into a generated xslt stylesheet as part of a
selct expression so that they can be evaluated.
And, any ideas how I could further improve the code above?
remove saxon:assign would be a good start!
saxon:assign is never necessary. (Declarative languages having the same
computational power as imperative ones)
David
________________________________________________________________________
The Numerical Algorithms Group Ltd is a company registered in England
and Wales with company number 1249803. The registered office is:
Wilkinson House, Jordan Hill Road, Oxford OX2 8DR, United Kingdom.
This e-mail has been scanned for all viruses by Star. The service is
powered by MessageLabs.
________________________________________________________________________
--~------------------------------------------------------------------
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>
--~--