Subject: Re: [xsl] Filtering, xslt 2.0 From: "Dave Pawson dave.pawson@xxxxxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> Date: Wed, 2 Nov 2022 13:01:34 -0000 |
On Wed, 2 Nov 2022 at 12:34, David Carlisle d.p.carlisle@xxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > > > > On Wed, 2 Nov 2022 at 12:13, Dave Pawson dave.pawson@xxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote: > You should use xs:string not xs:string* as if you passed in a sequence your later tokenize would fail. > > I'd do > > <xsl:param name="types" as="xs:string*"/> > <xsl:variable name="typesseq" as="xs:string*" select=" tokenize($types, ', *') /> > > Then use the sequence explicitly rather than relying on the optimiser to avoid tokenizing on every use. > > > <xsl:when test="type = $typesseq "> > > David Which seems to tokenize once rather than n times? Agreed more efficient (not a concern with my use) I don't understand select=" tokenize($types, ', *') The 'token' seems to be ,* where I tokenize on , only? Is that significant please? regards -- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ.
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] Filtering, xslt 2.0, David Carlisle d.p.c | Thread | Re: [xsl] Filtering, xslt 2.0, Martin Honnen martin |
Re: [xsl] Filtering, xslt 2.0, David Carlisle d.p.c | Date | Re: [xsl] Filtering, xslt 2.0, Martin Honnen martin |
Month |