From: Stephen Compall <s11@member.fsf.org>
To: guile-devel <guile-devel@gnu.org>
Subject: Re: [patch] SRFI-69 support
Date: Wed, 05 Dec 2007 22:24:50 -0600 [thread overview]
Message-ID: <1196915090.23906.12.camel@nocandy.dyndns.org> (raw)
In-Reply-To: <871wa03hi9.fsf@pobox.com>
[-- Attachment #1.1: Type: text/plain, Size: 1512 bytes --]
On Wed, 2007-12-05 at 23:26 +0100, Andy Wingo wrote:
> I know this is committed already (great work!), but perhaps you might be
> interested in some doc criticism:
Definitely! Patch inline below.
> > +By @dfn{coarser} than @code{equal?}, I mean that for all @var{x} and
I changed this to "we" instead to avoid a passive or more awkward form
such as "Coarser than equal? means that..."
--- doc/ref/srfi-modules.texi 3 Dec 2007 12:36:12 -0000 1.75
+++ doc/ref/srfi-modules.texi 6 Dec 2007 04:19:22 -0000
@@ -3091,11 +3091,11 @@
As a legacy of the time when Guile couldn't grow hash tables,
@var{start-size} is an optional integer argument that specifies the
-approximate starting size for the hash table. I will usually round
-this to an algorithmically-sounder number.
+approximate starting size for the hash table, which will be rounded to
+an algorithmically-sounder number.
@end deffn
-By @dfn{coarser} than @code{equal?}, I mean that for all @var{x} and
+By @dfn{coarser} than @code{equal?}, we mean that for all @var{x} and
@var{y} values where @code{(@var{equal-proc} @var{x} @var{y})},
@code{(equal? @var{x} @var{y})} as well. If that does not hold for
your @var{equal-proc}, you must provide a @var{hash-proc}.
--
Our last-ditch plan is to change the forums into a podcast, then send
RSS feeds into the blogosphere so our users can further debate the
legality of mashups amongst this month's 20 'sexiest' gadgets.
--Richard "Lowtax" Kyanka
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2007-12-06 4:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-01 20:30 [patch] SRFI-69 support Stephen Compall
2007-12-01 20:36 ` Stephen Compall
2007-12-03 12:40 ` Ludovic Courtès
2007-12-05 22:26 ` Andy Wingo
2007-12-06 4:24 ` Stephen Compall [this message]
2007-12-09 17:26 ` 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=1196915090.23906.12.camel@nocandy.dyndns.org \
--to=s11@member.fsf.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).