Robin,
> I'm quite sure you're sick of the sound of my typing by now,
Quite on the contrary, it sounds like heavenly music to us! :-)
(PS: Wrote this before I saw another bug report in the mail today...)
> but there's just one more thing I'd like to ask about.
> I think it's a bug, but the recommendation isn't (to my
> mind) quite clear about it.
>
> Sablotron throws an error if you declare a variable inside
> a for-each loop. The second time the loop is executed, you
> get "conflicting variable bindings".
Yes, I wasn't quite sure whether this is correct or not, and it seems it
isn't. The spec says:
(quote)
xsl:variable is allowed anywhere within a template that an instruction
is allowed. In this case, the binding is visible for all following
siblings and their descendants. Note that the binding is not visible for
the xsl:variable element itself.
(end)
Hence the binding made by an xsl:variable on the first pass through a
loop should be invisible to it on the second pass, causing no conflict.
Thanks a lot for your patch (a nice safe solution), we'll put it in the
next version. If you keep testing, keep sending us your observations
please - they're very valuable.
Best,
Tom
