Hi Mike,

>> Jeni wrote:
>> "There are two solutions that I can see:
>>
>> 1. ban using global variables in functions altogether
>>
>> 2. ban using global variables in functions that are called from the
>>    'match' attribute on xsl:template or the 'match' or 'use'
>>    attributes of xsl:key"
>
> References to global variables in a function called from these
> contexts (or from the select expression of another global variable)
> are no more troublesome than references to global variables in a
> template called from similar contexts.
>
> Circular references can already occur, despite the restrictions on
> variables in match attributes, and the processor has to cope with
> them already.

I'm happy to hear that it's not a problem; perhaps the restriction on
variable references in the attributes mentioned above could be lifted
in XSLT 1.1 or 2.0 - it would make some aspects of life a little
easier.

But I'm not sure I follow your argument. A template can't be called
from the 'match' attribute of xsl:template or the 'match' or 'use'
attributes of xsl:key.  So that would never be a problem anyway.

Cheers,

Jeni

---
Jeni Tennison
http://www.jenitennison.com/



 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list