From: Ken Raeburn <raeburn@raeburn.org>
To: Daniel Kraft <d@domob.eu>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: Elisp lexical-let
Date: Tue, 21 Jul 2009 17:46:02 -0400 [thread overview]
Message-ID: <DBD703E8-5C04-4B4B-9B56-EBFD3D03DDCC@raeburn.org> (raw)
In-Reply-To: <4A661B73.4090706@domob.eu>
On Jul 21, 2009, at 15:48, Daniel Kraft wrote:
> Especially, the question is about "what happens" when a lexical
> variable is inside its scope again bound dynamically (say via let or
> a lambda expression).
Oh, don't stop there... let's get some buffer-local or frame-local
bindings into the mix too! :-)
There are probably corner cases where the only "specification" you're
likely to find is "what Emacs does when you try it". And, if the goal
is to support the existing body of Lisp code (e.g., if Emacs 24 goes
out with lexical binding support, and people start using it), there's
a tradeoff between what seems logical or convenient to you, and what
behavior of Emacs the existing code is going to expect. Maybe not in
weird corner cases, but cases like you describe above seem likely, and
I think you'd want to mimic whatever behavior Emacs is going to do.
Ken
next prev parent reply other threads:[~2009-07-21 21:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-21 19:48 Elisp lexical-let Daniel Kraft
2009-07-21 21:46 ` Ken Raeburn [this message]
2009-07-22 9:11 ` Daniel Kraft
2009-07-22 13:00 ` Marijn Schouten (hkBst)
2009-07-22 19:24 ` Daniel Kraft
2009-07-23 15:24 ` Marijn Schouten (hkBst)
2009-07-23 16:13 ` Mark H Weaver
2009-07-23 20:53 ` Andy Wingo
2009-07-23 17:05 ` Daniel Kraft
2009-07-24 11:09 ` Marijn Schouten (hkBst)
2009-07-22 20:50 ` Ken Raeburn
2009-07-23 10:47 ` Daniel Kraft
2009-07-23 20:56 ` Andy Wingo
2009-07-24 6:50 ` Daniel Kraft
2009-07-23 20:49 ` Andy Wingo
2009-07-23 22:39 ` Andy Wingo
2009-07-24 7:08 ` Daniel Kraft
2009-07-24 11:42 ` Andy Wingo
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DBD703E8-5C04-4B4B-9B56-EBFD3D03DDCC@raeburn.org \
--to=raeburn@raeburn.org \
--cc=d@domob.eu \
--cc=guile-devel@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).