From: Andy Wingo <wingo@pobox.com>
To: Noah Lavine <noah.b.lavine@gmail.com>
Cc: guile-devel@gnu.org
Subject: Re: [PATCH] Possible Documentation Fix
Date: Sun, 30 Jan 2011 13:27:09 +0100 [thread overview]
Message-ID: <m3oc6y1srm.fsf@unquote.localdomain> (raw)
In-Reply-To: <AANLkTimuV=9vw4Gw+JCGfOegKNZVBhr4zqWnzFoXQND-@mail.gmail.com> (Noah Lavine's message of "Sat, 29 Jan 2011 13:08:50 -0500")
Hi Noah,
Thanks for the review and patch!
On Sat 29 Jan 2011 19:08, Noah Lavine <noah.b.lavine@gmail.com> writes:
> Could someone who understands syntax-case better than I do please
> review it for correctness?
It is correct, but I kinda liked the explicit mention of pattern
variable environments in the original. In syntax expansion, there are
lexical variables, bound in lexical environments, and pattern variables,
bound in syntax-expansion environments. The confusion addressed by that
paragraph was to treat a lexical variable as a pattern variable.
Also:
> +The reason this doesn't work is that the binding of @code{'it} established in
No need to quote symbols that are in @code{}.
Do you still think the discussion of environments is distracting?
Documentation should ulitimately be for users, and if the original text
is not useful at all, by all means we should change it.
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-01-30 12:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-29 18:08 [PATCH] Possible Documentation Fix Noah Lavine
2011-01-30 12:27 ` Andy Wingo [this message]
2011-01-31 19:54 ` Noah Lavine
2011-01-31 20:39 ` Andy Wingo
2011-02-02 14:53 ` Noah Lavine
2011-02-02 19:54 ` Andy Wingo
2011-02-02 20:09 ` Noah Lavine
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=m3oc6y1srm.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=noah.b.lavine@gmail.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).