> I think the biggest problem here is that the scope of a 
> variable is no longer obvious in these cases. This will also 
> impose an (hidden) order of evaluation, which is not the most 
> desirable feature for a non-imperative language.

The second sentence is nonsense. Variable references are resolved to
variable declarations at compile time, the run-time behavior doesn't
care in the slightest what the original name of the variable was.

Michael Kay
Software AG
home: Michael.H.Kay@xxxxxxxxxxxx
work: Michael.Kay@xxxxxxxxxxxxxx 


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