From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: compiler.texi: Compiling to the virtual machine
Date: Thu, 15 Jan 2009 23:03:20 +0100 [thread overview]
Message-ID: <m31vv41b2v.fsf@pobox.com> (raw)
In-Reply-To: <87fxjmltab.fsf@gnu.org> ("Ludovic Courtès"'s message of "Tue, 13 Jan 2009 23:45:16 +0100")
Hi Ludo,
Thanks for the review, it's appreciated. I've incorporated your vm.texi
changes and will push shortly.
On Tue 13 Jan 2009 23:45, ludo@gnu.org (Ludovic Courtès) writes:
> s/toplevel/top-level/
Ooh, this one is painful -- I feel like if it changes in the docs it
should change in the code too. Do you really think this is the right
thing? top-level-ref ? <ghil-top-level-env> ?
> s/runtime/run-time/
So, to me:
"run-time" sounds better as an adjective, and as a noun meaning "when
code is executed"; and
"runtime" sounds better for "the libguile runtime".
I've sprinkled appropriate changes. Let me know if it still reads wrong.
> s/e.g./e.g.,/
To me, s/e.g./for example/ is an idempotent transformation. So if the
clause after "e.g." is short, no comma necessary. Otherwise you need a
comma for breath. But maybe it is a snooty style.
>> @node Extending the Compiler
>> @subsection Extending the Compiler
>
> I like this section. :-)
Hah! Junkie :-)
>> recommended papers: Dybvig's HOCS, Ghuloum's compiler paper.
Ah yes, this was an oversight. I'll fix.
Thanks again!
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2009-01-15 22:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-11 17:37 compiler.texi: Compiling to the virtual machine Andy Wingo
2009-01-13 22:45 ` Ludovic Courtès
2009-01-15 22:03 ` Andy Wingo [this message]
2009-01-17 23:12 ` Ludovic Courtès
2009-01-19 20:43 ` Ken Raeburn
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=m31vv41b2v.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=ludo@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).