This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: Re: Assignment no, dynamic scoping si (was: Wishes for XSL revisions ...
- From: Dimitre Novatchev <dnovatchev at yahoo dot com>
- To: xsl-list at lists dot mulberrytech dot com
- Date: Mon, 31 Dec 2001 22:20:14 -0800 (PST)
- Subject: [xsl] Re: Re: Assignment no, dynamic scoping si (was: Wishes for XSL revisions ...
- Reply-to: xsl-list at lists dot mulberrytech dot com
terje at in-progress dot com (Terje Norderhaug) wrote:
> >
> >It is obvious that any function with implicit parameters cannot be used as a
first
> >class object (e.g. passed as parameter to other functions, or returned as their
> >result). Such functions will be difficult to combine with other functions and
> >generally to reuse.
>
> I suspect you are mistaken. Using function with implicit parameters as a first
> class objects works fine in Common LISP, where implicit parameters will be
> captured in a closure that has the same extent as the function object.
No, I'm not mistaken. Read the article at:
http://citeseer.nj.nec.com/cache/papers/cs/11502/http:zSzzSzwww.cse.ogi.eduzSz~mbszSzpubzSzimplicit.pdf/lewis00implicit.pdf
In section 6. at the end of the left column on page 10 the authors say:
"Implicit parameters provide the same functionality as dynamic scoping in Lisp,
except that implicitly parameterized functions are not first-class, and thus can't
be passed as arguments to functions... Thus, we would argue that implicit parameters
give you the best of dynamic scoping, while avoiding its worst pitfalls."
Cheers,
Dimitre Novatchev.
__________________________________________________
Do You Yahoo!?
Send your FREE holiday greetings online!
http://greetings.yahoo.com
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list