From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: vm.texi: A virtual machine for guile
Date: Tue, 13 Jan 2009 23:30:09 +0100 [thread overview]
Message-ID: <87r636ltzi.fsf@gnu.org> (raw)
In-Reply-To: m3pritn3ri.fsf@pobox.com
Hello!
You rock! I didn't read it in details, but I'm amazed by the clarity of
the explanations and the level of details, so thank you!
A bit of nitpicking since it's what I'm good at:
Andy Wingo <wingo@pobox.com> writes:
> Guile has both an interpreter and a compiler. To a user, the
> difference is largely transparent -- interpreted and compiled
I think "transparent---interpreted" yields the typographically correct
output in Info/TeX.
> For a long time, Guile only had an interpreter, called the evaluator.
Maybe "@defn{evaluator}" and perhaps also an `@cindex'.
> values, call/cc) and can provide optimized inline instructions for
> Guile (cons, struct-ref, etc.).
A couple of `@code' here.
Other than these small formatting issues, the material appears to be
very good to me.
Keep up the good work! :-)
Ludo'.
prev parent reply other threads:[~2009-01-13 22:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-11 17:36 vm.texi: A virtual machine for guile Andy Wingo
2009-01-13 22:30 ` Ludovic Courtès [this message]
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=87r636ltzi.fsf@gnu.org \
--to=ludo@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).