unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Daniel Kraft <d@domob.eu>
To: Ken Raeburn <raeburn@raeburn.org>
Cc: Andy Wingo <wingo@pobox.com>,
	Neil Jerram <neil@ossau.uklinux.net>,
	guile-devel <guile-devel@gnu.org>
Subject: Re: Elisp flet construct
Date: Tue, 21 Jul 2009 21:32:41 +0200	[thread overview]
Message-ID: <4A6617D9.70705@domob.eu> (raw)
In-Reply-To: <842CDAEA-54F2-496D-ADCC-3B191AA7771D@raeburn.org>

Hi Ken,

Ken Raeburn wrote:
> On Jul 21, 2009, at 09:10, Daniel Kraft wrote:
>> Just a little addition to the subject of extensions:  I'd very much 
>> like to add lexical-let and lexical-let* as another set of extensions, 
>> because this gives the possibility to use "fast" lexical variables 
>> without the dynamic-scoping-fluid-pain.
>>
>> Currently, I did implement some control constructs that could be done 
>> as macros still in the compiler directly (like prog1 or dolist) 
>> because there I can make use of lexical helper variables; lexical-let 
>> would allow using this feature directly from elisp (and implementing 
>> these constructs equivalently as macros).
>>
>> So, what do you think about this extension?
> 
> Is this modeled on the lexical-let work being done for Emacs (probably 
> to be merged for Emacs 24)?  If so, I wouldn't call it an extension so 
> much as being compatible in advance. :-)  And if not, you should 
> probably take a look at that work and make sure yours is compatible.

hm...  I just found this page which is not decidedly about a planned 
addition to emacs 24, but I think it is quite reasonable that this 
addition will be the extension/feature described here:

http://www.delorie.com/gnu/docs/emacs/cl_21.html

This seems also (as far as I'm no expert on the details) to be just like 
let behaves in Scheme and I plan to implement lexical-let just using 
Guile's real let handling (not the dynamic one based on fluids crafted 
for elisp) -- I hope this is "compatible".

If this is not quite correct, please point me to another source and/or 
let me know the differences between Scheme's let to keep in mind!

Thanks, Daniel

-- 
Done:  Arc-Bar-Cav-Ran-Rog-Sam-Tou-Val-Wiz
To go: Hea-Kni-Mon-Pri




  reply	other threads:[~2009-07-21 19:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-20 17:53 Elisp flet construct Daniel Kraft
2009-07-21 13:10 ` Daniel Kraft
2009-07-21 18:35   ` Ken Raeburn
2009-07-21 19:32     ` Daniel Kraft [this message]
2009-07-21 21:33       ` Ken Raeburn
2009-07-23 20:46   ` Andy Wingo
2009-07-23 21:53     ` Ken Raeburn
2009-07-23 22:50       ` Andy Wingo
2009-07-24  6:38     ` Daniel Kraft
2009-07-23 20:44 ` Andy Wingo
2009-07-24  6:26   ` 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

  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=4A6617D9.70705@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).