RE: nested templates?

>But, hypothetically, what would be the difference between these
>hypothetical nested-and-scoped templates, and the not-so-hypothetical (but
>often misapplied, and hence warned-against) xsl:for-each?

Well probably not much really you can do anything with anything but I guess
it's just a view of the playing field. for-each restricts you to a one
dimensional view of things unless you use it to change context (the playing
field you are on). But then you should call it something else. Team-bus
comes to mind.
I think nested templates could be quite powerful and a lot more logical.

>I suppose it would be okay for beginners to use nested templates? :->

Hey why not? But then they would be using them for different reasons than
for-each

I think it would make things a little less verbose and implementation surely
wouldn't be that difficult. Just a couple more levels on the stack.

I dunno it just seems more logical for some situations. I haven't thought it
through though. It just struck me as  something that should be. I guess
there is a reason why it wasn't allowed.

Ciao Chris

XML/XSL Portal
http://www.bayes.co.uk/xml


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