Re: [xsl] Re: Assignment no, dynamic scoping si (was: Wishes forXSL revisions ...

[Mike Haarman <mhaarma at atlas dot socsci dot umn dot edu>]

On Fri, 28 Dec 2001, Gunther Schadow wrote:

> Dimitre Novatchev wrote:

[snip]

> > One alternative is to switch to a better functional language
> > (e.g. Haskell), use HaXML and forget about XSLT. This however
> > will likely not appeal to you as Haskell's variables are immutable
> > too...

[snip]

> There is no question about side-effects and global variables in
> the imperative programming style. I didn't ask for any of this
> to be added to XSLT. What I was asking for was dynamic scoping,
> at least an option to be able to use dynamic scoping for some
> variables. I also said that without dynamic scoping I could see
> little reason for calling variables variables, because they are
> fixed value bindings that I could just simply lexically substitute
> wherever they are used (except where an RTF is constructed.)
>

It should be possible to give a semblance of dynamic scoping by wrapping
your processor in a class which maintains access to and value of symbols
which the stylesheet references via an extension.  I should think.  I've
never done anything like this in practice.  What are the limitations to
such an approach?


Mike Haarman -- mhaarma@socsci.umn.edu
College of Liberal Arts   University of Minnesota, Minneapolis, West Bank


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