[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: Transitive closure for XPath
> Cute. Presumably as well as > closure(/closure/node[1], id(@child)) > you could have > closure(/closure/node[1], key("myKey", @child)) > You need delayed evaluation of parameters. Is this straightforward in > other XSLT engines? That's the one thing that is a bit worrying, the repeated and delayed evaluation of the same parameter. It was straightfoward enough in Xalan (although I had to override the default method, which evaluates the parameters before passing them to the function). I have not even attempted to understand the implications of this for optimised queries. I am not an expert in XPath details, so I wonder how feasible it would be to disguise this as an axis: /*/node[1]/closure::id(./@child) ? A function is definitely much easier to implement though. > (Of course I'd like to rename it to expand-o-graph() since that's how I > visualise its operation) Yes, or bounded avalanche operator :) Christian XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|