From: David Kastrup <dak@gnu.org>
To: guile-devel@gnu.org
Subject: Re: Anything better for delayed lexical evaluation than (lambda () ...)?
Date: Wed, 14 Dec 2011 15:27:45 +0100 [thread overview]
Message-ID: <87y5uf8bz2.fsf@fencepost.gnu.org> (raw)
In-Reply-To: 87wr9zntv0.fsf@gnu.org
ludo@gnu.org (Ludovic Courtès) writes:
> Andy Wingo <wingo@pobox.com> skribis:
>
>> But, in the event that David wants to continue with his current
>> strategy, there are other things that can be done. David, did you know
>> that Guile's evaluator is implemented in Scheme? That means that if you
>> want an evaluator with different semantics -- for example, something
>> closer to Kernel[0], as David appears to want -- then you can implement
>> an evaluator that provides for fexprs and the like, and it will run
>> about as well as Guile's evaluator.
>
> Indeed. FWIW, Skribilo [0] has its own input language, which is similar
> to but different from Scheme, so it has its own reader and its own
> evaluator, the latter being mostly a wrapper around ‘eval’. This
> strategy has worked well, and portably between 1.8 and 2.0.
There is a saying "a real FORTRAN programmer can write FORTRAN programs
in any language". But one of the principal attractions of implementing
a Scheme-like language in Scheme is that one can _turn_ Scheme into
one's target language instead of merely using it as an implementation
language.
In contrast, you usually don't implement a C-like language by
manipulating your C compiler (some template libraries may come close),
and you usually do not even want to bootstrap a FORTRAN compiler on
FORTRAN.
And in particular for something like Emacs Lisp, it would be quite more
interesting to turn GUILE into Emacs Lisp rather than implement Elisp on
top of it. I have not actually looked at the respective code bases.
That's just a gut feeling of what would be cool, and also provide a user
experience that is not purely either/or regarding what layer one is
working in.
--
David Kastrup
next prev parent reply other threads:[~2011-12-14 14:27 UTC|newest]
Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-03 15:45 Anything better for delayed lexical evaluation than (lambda () ...)? David Kastrup
2011-12-03 16:44 ` Andy Wingo
2011-12-06 14:55 ` Thien-Thi Nguyen
2011-12-06 15:45 ` David Kastrup
2011-12-06 19:50 ` Marco Maggi
2011-12-11 9:33 ` David Kastrup
2011-12-11 9:51 ` David Kastrup
2011-12-12 5:21 ` Mark H Weaver
2011-12-12 6:47 ` David Kastrup
2011-12-12 18:29 ` Mark H Weaver
2011-12-12 19:56 ` David Kastrup
2011-12-12 20:39 ` rixed
2011-12-12 21:02 ` David Kastrup
2011-12-12 21:58 ` Mark H Weaver
2011-12-12 21:40 ` Mark H Weaver
2011-12-12 21:50 ` Andy Wingo
2011-12-13 9:02 ` David Kastrup
2011-12-13 13:05 ` Andy Wingo
2011-12-13 13:56 ` David Kastrup
2011-12-13 14:34 ` Andy Wingo
2011-12-13 15:27 ` David Kastrup
2011-12-13 15:48 ` Andy Wingo
2011-12-13 16:08 ` David Kastrup
2011-12-13 16:27 ` Andy Wingo
2011-12-13 16:54 ` David Kastrup
2011-12-13 18:58 ` Andy Wingo
2011-12-13 22:23 ` David Kastrup
2011-12-13 17:28 ` Mark H Weaver
2011-12-13 18:49 ` Andy Wingo
2011-12-13 19:15 ` Mark H Weaver
2011-12-13 23:00 ` Noah Lavine
2011-12-13 23:16 ` David Kastrup
2011-12-13 23:44 ` Andy Wingo
2011-12-13 23:39 ` Andy Wingo
2011-12-13 23:45 ` David Kastrup
2011-12-14 10:15 ` Andy Wingo
2011-12-14 10:32 ` David Kastrup
2011-12-14 0:30 ` Mark H Weaver
2011-12-14 8:16 ` David Kastrup
2011-12-14 0:42 ` Noah Lavine
2011-12-14 0:47 ` Noah Lavine
2011-12-14 1:30 ` Mark H Weaver
2011-12-14 7:50 ` Mark H Weaver
2011-12-14 8:48 ` [PATCH] Implement `capture-lexical-environment' in evaluator Mark H Weaver
2011-12-14 9:08 ` David Kastrup
2011-12-14 9:36 ` Mark H Weaver
2011-12-16 9:21 ` [PATCH] Implement `the-environment' and `local-eval' " Mark H Weaver
2011-12-16 9:32 ` David Kastrup
2011-12-16 14:00 ` Peter TB Brett
2011-12-16 14:26 ` David Kastrup
2011-12-16 15:27 ` Mark H Weaver
2011-12-16 16:01 ` Andy Wingo
2011-12-16 17:44 ` Mark H Weaver
2011-12-16 19:12 ` Mark H Weaver
2012-01-07 1:26 ` Andy Wingo
2012-01-07 17:30 ` Mark H Weaver
2012-01-07 1:18 ` Andy Wingo
2011-12-16 16:59 ` Hans Aberg
2011-12-14 10:08 ` Anything better for delayed lexical evaluation than (lambda () ...)? Andy Wingo
2011-12-14 10:27 ` David Kastrup
2011-12-14 13:35 ` Andy Wingo
2011-12-14 15:21 ` David Kastrup
2011-12-14 15:55 ` Andy Wingo
2011-12-14 17:26 ` Mark H Weaver
2011-12-14 18:23 ` David Kastrup
2011-12-14 18:38 ` Mark H Weaver
2011-12-14 19:14 ` David Kastrup
2011-12-14 19:44 ` David Kastrup
2011-12-14 22:56 ` Andy Wingo
2011-12-14 11:03 ` Mark H Weaver
2011-12-14 11:18 ` David Kastrup
2011-12-14 13:31 ` Noah Lavine
2011-12-14 21:03 ` Mark H Weaver
2011-12-14 22:12 ` David Kastrup
2011-12-14 22:24 ` David Kastrup
2011-12-14 22:55 ` Andy Wingo
2011-12-13 16:24 ` David Kastrup
2011-12-13 15:52 ` David Kastrup
2011-12-13 11:14 ` David Kastrup
2011-12-14 13:52 ` Ludovic Courtès
2011-12-14 14:27 ` David Kastrup [this message]
2011-12-14 21:30 ` Ludovic Courtès
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=87y5uf8bz2.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--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).