Hi,
If the keyword list could be used elsewhere, it should certainly be in a
variable.
What would be the most performance efficient way to handle the case, in
xslt2?
Are there alternatives that would not offer as "equally bad" performance?
- Setting up key(s)?
- making keywords a space separated list so that a single "contains()"
invocation is required on a "match"?
Thanks,
ac
...more simply?
<xsl:template match="item[description = ('word1', 'word2', 'word3')]">
.. process the item ..
</xsl:template>
Is there a performance advantage to the variable or is the
match pattern sequence optimized anyway (e.g. Saxon)?
Shouldn't make any difference performance-wise (both equally bad...). But he
said he wanted the word list in a separate place for maintainability.
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>
--~--
--~------------------------------------------------------------------
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>
--~--