Re: [xsl] Filtering, xslt 2.0

["Eliot Kimber eliot.kimber@xxxxxxxxxxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>]

The second argument to tokenize() is a regular expression, so , * means
comma followed by zero or more spaces.

I would write it as ,\s*, which is clearer and handles all white space
(space, tab, etc.).

Cheers,

E.

_____________________________________________
Eliot Kimber
Sr Staff Content Engineer
O: 512 554 9368
M: 512 554 9368
servicenow.com<https://www.servicenow.com>
LinkedIn<https://www.linkedin.com/company/servicenow> |
Twitter<https://twitter.com/servicenow> |
YouTube<https://www.youtube.com/user/servicenowinc> |
Facebook<https://www.facebook.com/servicenow>

From: Dave Pawson dave.pawson@xxxxxxxxx
<xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>
Date: Wednesday, November 2, 2022 at 8:46 AM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx <xsl-list@xxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: [xsl] Filtering, xslt 2.0
[External Email]

On Wed, 2 Nov 2022 at 13:11, Martin Honnen martin.honnen@xxxxxx
<xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:


> > 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?
> >
> >
> >
>
>
> I would say it depends on your input data, if you know for sure (and on
> the command line with a parameter it is likely) that you always have
> only the comma as a separator and no (optional) spaces then you can
> tokenize on the "," alone safely.

Which in my case makes sense option A or B or C (A,B,C) which is simple?

> I guess David wanted to cater for e.g.
> "a, b, c" e.g. comma plus spaces between tokens.

So ",*" is acting as comma followed by wildcard?
(not even regex is it?)

Being v.suspicious of David and his mathematical mind, it wouldn't surprise
me if he has other aspects in mind :-)

regards


--
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.