From: pjb@informatimago.com (Pascal J. Bourguignon)
To: help-gnu-emacs@gnu.org
Subject: Re: lexical-let detail semantics
Date: Mon, 27 Jul 2009 15:16:44 +0200 [thread overview]
Message-ID: <7c63deuuyr.fsf@pbourguignon.anevia.com> (raw)
In-Reply-To: mailman.3248.1248688520.2239.help-gnu-emacs@gnu.org
Daniel Kraft <d@domob.eu> writes:
> Hi,
>
> I'm working on an implementation of elisp for GNU Guile, and want to
> include the lexical-let construct from the Common Lisp Extensions of
> elisp. There are some details of its semantics I'm not sure about and
> that are not clarified in the documentation of lexical-let, so I had
> to do some experiments. Here are two questions that came up during
> these where I'd love to hear comments from regular elisp users:
>
>
> 1) let within lexical-let:
>
> (setq a 1)
> (defun dyna () a)
> (lexical-let ((a 2))
> (let ((a 3))
> (print (dyna))))
> => 1
If you have a look at the macro expansion of lexical-let, it looks
like it is the intended behavior.
(macroexpand '(lexical-let ((a 2))
(let ((a 3))
(print (dyna)))))
--> (let ((--cl-a-- 2)) (letf (((symbol-value (quote --cl-a--)) 3)) (print (dyna))))
> My first thought was that a let within the lexical scope of another
> lexical-let would revert the symbols to dynamic scoping again, but it
> seems that let behaves just as if it was lexical-let for symbols
> already lexically bound.
>
> Is this 'expected behaviour' or something 'by chance'? Do you think
> it is necessary for compatibility with (most) existing code to mimic
> this behaviour or would it be ok for the code above to print 3?
I agree, it's not what I'd expect either.
Have a look at the Common Lisp reference:
http://www.lispworks.com/documentation/HyperSpec/Body/s_let_l.htm
http://www.lispworks.com/documentation/HyperSpec/Body/d_specia.htm
I would translate the above forms in Common Lisp as:
(SETF (SYMBOL-VALUE 'A) 1)
(DEFUN DYNA ()
(DECLARE (SPECIAL A))
A)
(LET ((A 2))
(LET ((A 3))
(DECLARE (SPECIAL A))
(PRINT (DYNA))))
prints: 3
--> 3
You can avoid the problem by putting the dynaminc bindings outside of
reach of lexical-let:
(defun call-dyna ()
(let ((a 3)) (print (dyna))))
(lexical-let ((a 2))
(call-dyna))
prints: 3
--> 3
Notice also that in languages that have both special variables and
lexical variables, it is found worthwhile to keep them in separate
name spaces. In ISO-LISP, this is done with the (dynamic var) form
for special variables. In Common Lisp it's done with the *earmuff*
convention.
(defvar *a* 1)
(defun dyna ()
(print *a*))
(lexical-let ((a 2))
(let ((*a* 3))
(dyna)))
prints: 3
--> 3
which is what we expect:
(macroexpand '(lexical-let ((a 2))
(let ((*a* 3))
(dyna))))
--> (let ((--cl-a-- 2)) (let ((*a* 3)) (dyna)))
You may report the bug to the maintainers, but I'm not sure it's
worthwhile. If you want a real language, perhaps you could use
emacs-cl? http://www.lisp.se/emacs-cl/
> In contrast, the code:
>
> (setq a 1)
> (defun dyna () a)
> (lexical-let ((a 2))
> ((lambda (a)
> (print (dyna))) 3))
> => 3
>
> does indeed revert a to dynamic binding... This seems somewhat
> inconsistent to me (although of course argument-lists and let's are
> not really the same thing).
Yes, there's a (theorical) equivalence between lambda and let.
In this case again the macroexpansion explains why it works:
(macroexpand '(lexical-let ((a 2))
((lambda (a)
(print (dyna))) 3)))
--> (let ((--cl-a-- 2)) (funcall (function (lambda (a) (print (dyna)))) 3))
> 2) Closures:
>
> I'm happy that lexical-let works well to build closures (and in fact
> it seems that this is the main intention for lexical-let at all);
> however this code does not work as expected:
>
> (setq a 1)
> (lexical-let ((a 2))
> ((lambda () (print a))))
> => 1
>
> I don't know why, but it seems that calling a closure directly fails,
> while storing it and calling it later succeeds (as in the examples at
> http://www.delorie.com/gnu/docs/emacs/cl_21.html for instance). Is
> this a bug or again something expected? If the latter, what's the
> exact rationale and semantics then?
I guess you have a bug in your version. Mine works ok.
Again, the macroexpansion explains what lexical-let does in this case:
(macroexpand '(lexical-let ((a 2))
((lambda () (print a)))))
--> (let ((--cl-a-- (make-symbol "--a--")))
(setf (symbol-value --cl-a--) 2)
(funcall (list (quote lambda) (quote (&rest --cl-rest--))
(list (quote apply)
(function (lambda (G93796) (print (symbol-value G93796))))
(list (quote quote) --cl-a--)
(quote --cl-rest--)))))
In emacs-version "22.2.1", I get the right result:
(lexical-let ((a 2))
((lambda () (print a))))
prints: 2
--> 2
--
__Pascal Bourguignon__
next prev parent reply other threads:[~2009-07-27 13:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.3248.1248688520.2239.help-gnu-emacs@gnu.org>
2009-07-27 10:50 ` lexical-let detail semantics A.Politz
2009-07-27 12:09 ` Daniel Kraft
2009-07-27 13:16 ` Pascal J. Bourguignon [this message]
2009-07-27 14:44 ` Daniel Kraft
[not found] ` <mailman.3293.1248739037.2239.help-gnu-emacs@gnu.org>
2009-07-28 0:48 ` Pascal J. Bourguignon
2009-07-27 9:50 Daniel Kraft
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7c63deuuyr.fsf@pbourguignon.anevia.com \
--to=pjb@informatimago.com \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.