Re: Nicer way to change context-node than xsl:for-each

> If a change in context was required for call-template, I might have
> modeled this, by having another parameter for *[1] on call-template
> (which might be a better design decision, as it encourages loose
> coupling!), instead of modeling this requirement as a loop.

yes or make it a match template instead of named. But still It's not
uncommon for me to find myself with a largeish called template with,
within its code lots of implicit assumtions on the current nde. And when
you find yourself needing to call that in another context wrapping it in
xsl:for-each is often the least intrusive change.

David


________________________________________________________________________
The Numerical Algorithms Group Ltd is a company registered in England
and Wales with company number 1249803. The registered office is:
Wilkinson House, Jordan Hill Road, Oxford OX2 8DR, United Kingdom.

This e-mail has been scanned for all viruses by Star. The service is
powered by MessageLabs. 
________________________________________________________________________