From: Daniel Kraft <d@domob.eu>
To: Ken Raeburn <raeburn@raeburn.org>
Cc: Andy Wingo <wingo@pobox.com>, guile-devel <guile-devel@gnu.org>,
Neil Jerram <neil@ossau.uklinux.net>
Subject: Re: Elisp lexical-let
Date: Thu, 23 Jul 2009 12:47:21 +0200 [thread overview]
Message-ID: <4A683FB9.50806@domob.eu> (raw)
In-Reply-To: <F88A3E64-7F70-48A8-9D28-8D229C3E9056@raeburn.org>
Ken Raeburn wrote:
> On Jul 22, 2009, at 05:11, Daniel Kraft wrote:
>> It seemed really hard to me to find at least *basic* information about
>> how the lexbind things works; I did build now an emacs with lexbind
>> from trunk, but so far as I see this is not meant to implement
>> "lexical-let" as the cl package does, but rather allows switching all
>> bindings from dynamic to lexical within one source file.
>
> Oh... I may have seriously misunderstood; sorry about that. That's what
> comes from not having bothered to look. :-)
Ok, I think I'll work on a cl like lexical-let now and see what this
gives in performance related to dynamic let (and just to get it
available of course).
The implementation will (for now at least) be as I favour it, that is,
inner lets revert to dynamic binding (as do inner lambdas for their
arguments) -- this is more reasonable (I think), has more power (as the
other way can be achieved by using lexical-let for inner lets when
preferred, which is also clearer to understand) and should be easier to
implement (because I don't need to mess around with the compilation of
let constructs depending on the context).
I'll keep in mind also the lexbind idea of optionally making every
binding lexical. Andy, can you give me a hint/example/pointer how
compiler options work? This would be exactly the place to provide this,
I think. Additionally we could add an option to remove the "variable is
void" error check for a further performance gain.
Yours,
Daniel
--
Done: Arc-Bar-Cav-Ran-Rog-Sam-Tou-Val-Wiz
To go: Hea-Kni-Mon-Pri
next prev parent reply other threads:[~2009-07-23 10:47 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
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 [this message]
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=4A683FB9.50806@domob.eu \
--to=d@domob.eu \
--cc=guile-devel@gnu.org \
--cc=neil@ossau.uklinux.net \
--cc=raeburn@raeburn.org \
--cc=wingo@pobox.com \
/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).