Subject: Re: Assignment no, dynamic scoping si (was: Re: [xsl] RE: Wishes for XSL revisions ... From: David Carlisle <davidc@xxxxxxxxx> Date: Tue, 1 Jan 2002 13:14:01 GMT |
> The only way XSLT gives you to deal with that problem is to > make *every* of those layout parameters explicit parameters > to *every* template. "only" ? if they are fixed for a given run as is probably the case for your text width example, then they can be "global variablesd (or parameters). Also if you find declaring loits of parameters inconvenient you always have the option of just declaring one tree valued parameter and extracting whatever data you need from that. (This is easier to set up in xslt 2.0 draft but is also perfectly possible in xslt 1.0) I'm not saying dynamic scope is necessarily a bad idea, although I don't think it would fit so easily into the current xslt design, but your arguments for adding such a feature are not strengthened if you over-state the problems with the current design. David _____________________________________________________________________ This message has been checked for all known viruses by Star Internet delivered through the MessageLabs Virus Scanning Service. For further information visit http://www.star.net.uk/stats.asp or alternatively call Star Internet for details on the Virus Scanning Service. XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
[xsl] Re: Re: Assignment no, dynami, Dimitre Novatchev | Thread | RE: Assignment no, dynamic scoping , Evan D. Lenz |
[xsl] Re: Re: Assignment no, dynami, Dimitre Novatchev | Date | [xsl] Footnotes, for a learner., Michel Guay |
Month |