Subject: Re: xsl:key From: David Carlisle <davidc@xxxxxxxxx> Date: Thu, 4 May 2000 00:03:06 +0100 (BST) |
> What's the point of doing: > ... > if the xsl:key is not a static hashtable ? none, I think. Like id, key is replaceable by some construction selecting nodes based on an xpath expression, so you just have to trust that the implementors implement it at least no less efficiently than that. Perhaps a hash table is made for each included document() based on all the current xsl:keys in effect. You'd have to ask the implementors though (or look at the code, but looking at the code isn't my style:-) That's how it works for id() after all. The implied hash table of id values is per-document and you can switch the current document by using (for example) xsl:for-each. This seems to be the implication of the example in the spec that you quote. David XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: xsl:key, Michael French | Thread | Re: xsl:key, David Marston/CAM/Lo |
Re: expression value not a node set, Mike Brown | Date | RE: IE 5.0 Mac, FileMaker Pro, & HT, Jonathan Marsh |
Month |