Re: [xsl] Value of variable not appearing in the <xsl:otherwise> of xml:choose

["Wendell Piez wapiez@xxxxxxxxxxxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>]

Hi again,

What Graydon says is totally true, but the counter is also true, that it
can be amazing what grouping *can* be made to do and problems it can solve
that you didn't think were grouping problems but actually are.

This actually includes overlap problems, as Gerrit (just to name one) has
also shown. One of my favorite patterns is group-adjacent with a function
as a grouping key.

Cheers, Wendell




On Wed, Sep 22, 2021 at 1:17 PM Graydon graydon@xxxxxxxxx <
xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:

> On Wed, Sep 22, 2021 at 05:06:34PM -0000, Wendell Piez
> wapiez@xxxxxxxxxxxxxxx scripsit:
> > Another optimization to consider is to group using
> > group-adjacent="@class='analyze_visual'" returning a Boolean grouping
> key,
> > and groups that are nicely split.
> >
> > Then part/@num should collapse into '{position()}' and things get
> simpler.
> > Also gracefully handles the case of multiple splits.
>
> Especially if you find Wendell's observation above covers your use
> cases, it won't apply this time, but in general, I find that if I'm
> struggling with xsl:for-each-group, I should -- and sometimes I even do!
> -- remember that xsl:for-each-group is not fully general. There comes a
> time to write one's own recursive grouping function for this particular
> case.
>
> Which sounds awful, but is generally much simpler than it feels like it
> ought to be and is highly preferable to trying to make
> xsl:for-each-group cover a case it can't cover.
>
> --
> Graydon Saunders  | graydonish@xxxxxxxxx
> CC&s oferC)ode, C0isses swC! mC&g.
> -- Deor  ("That passed, so may this.")
>
>
>

--
...Wendell Piez... ...wendell -at- nist -dot- gov...
...wendellpiez.com... ...pellucidliterature.org... ...pausepress.org...
...github.com/wendellpiez... ...gitlab.coko.foundation/wendell...