On Sun, 2021-06-20 at 00:35 +0000, Graydon graydon(_at_)marost(_dot_)ca wrote:
I think this is one of those places where the imperative best
practise
and the declarative best practise aren't perfectly congruent.
For sure things are changed, but recall that global variables in XSLT
can be overriden. At least unless they are marked final.
But i agree there are cases where it makes sense. Sometimes i write,
<xsl:variable name="input" select="/" />
for example, and although this could as well be a tunnel parameter, i
often find global variables easier to find.
Liam
--
Liam Quin, https://www.delightfulcomputing.com/
Available for XML/Document/Information Architecture/XSLT/
XSL/XQuery/Web/Text Processing/A11Y training, work & consulting.
Barefoot Web-slave, antique illustrations: http://www.fromoldbooks.org
--~----------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
EasyUnsubscribe: http://lists.mulberrytech.com/unsub/xsl-list/1167547
or by email: xsl-list-unsub(_at_)lists(_dot_)mulberrytech(_dot_)com
--~--