unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: compiler.texi: Compiling to the virtual machine
Date: Sun, 18 Jan 2009 00:12:35 +0100	[thread overview]
Message-ID: <87d4elr0gs.fsf@gnu.org> (raw)
In-Reply-To: m31vv41b2v.fsf@pobox.com

Hey!

Andy Wingo <wingo@pobox.com> writes:

> 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> ?

Code and documentation are two different things IMO.  You could write
"top-level" in English text and use "toplevel" in identifiers if you
find it more appropriate.

>>   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.

I dunno, I thought the comma was sort of compulsory.

A quick googling reveals that opinions diverge, but that the comma after
"e.g." is often used in American English.

Thanks,
Ludo'.





  reply	other threads:[~2009-01-17 23:12 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
2009-01-17 23:12     ` Ludovic Courtès [this message]
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=87d4elr0gs.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).