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: r6rs library documentation
Date: Tue, 22 Jun 2010 14:15:00 +0200	[thread overview]
Message-ID: <87ocf3l0vv.fsf@gnu.org> (raw)
In-Reply-To: AANLkTil3TtF5jDAaRKMh6l2clhbjyKobFHlySJg8jRsQ@mail.gmail.com

Hi Julian,

Julian Graham <joolean@gmail.com> writes:

>> Sounds great to me, though Brian & Neil can always come in to correct me
>> :)
>
> Done!  See commit ea28e981342fd1d381e489e57cddde97eb390442.  In
> addition to the main .texi payload, I adjusted the formatting on some
> of your initial paragraphs and removed the descriptions of the base
> and composite libraries -- let me know if those changes are
> problematic.

Great work!  I find it nice and convenient to have all this in the
manual.

Random remarks:

  +@deffn {Scheme Procedure} fold f lst1 lst2 ...
  +@deffnx {Scheme Procedure} for-each f lst1 lst2 ...
  +@xref{SRFI-1 Fold and Map}, for documentation.
  +@end deffn

There’s no ‘fold’ in R6RS-lib; it’s called ‘fold-left’.

  +@deffnx {Scheme Procedure} remq obj list
  +@code{remove}, @code{remv}, and @code{remq} are identical to the
  +@code{delete}, @code{delv}, and @code{delq} procedures provided by
  +Guile's core library; (@pxref{List Modification}) for their

Should be “Guile’s core library (@pxref{List Modification}).”

  +@deffn {Scheme Procedure} div x1 x2
  +@deffnx {Scheme Procedure} mod x1 x2
  +@deffnx {Scheme Procedure} div-and-mod x1 x2
  +These procedures implement number-theoretic division.

How about this instead:

  @code{div} is an alias for Guile’s @code{quotient} and @code{mod} is
  an alias for @code{modulo} (@pxref{Integer Operations}).


  +The manual sections below describe Guile's implementation of R6RS
  +records, which provide support for user-defined data types. The R6RS
  +records API provides a superset of the features provided by Guile's
  +``native'' records, as well as those of the SRFI-9 records API;
  +(@pxref{Records}) and (@pxref{SRFI-9}) for a description of those
  +interfaces.

This use of @pxref is incorrect and leads to broken rendering with all
back-ends (info "(texinfo) pxref").  The same problem appears in other
places.  Could you look into it?

  +@node rnrs conditions
  +@subsubsection rnrs conditions

Perhaps add an xref to SRFI-35, in pure TIMTOWTDI spirit.  ;-)

  +Compound conditions do not ``nest'' --- constructing a new compound

The ‘---’ should not be surrounded by spaces.  Though according to
https://secure.wikimedia.org/wikipedia/en/wiki/Dash#Em_dash you could
argue that you’re following the /The New York Times Manual of Style and
Usage/.  ;-)

  +@node rnrs arithmetic bitwise
  +@subsubsection rnrs arithmetic bitwise

Add link to SRFI-60?

Thanks!

Ludo’.




  reply	other threads:[~2010-06-22 12:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-05  4:57 r6rs library documentation Julian Graham
2010-05-05 21:12 ` Ludovic Courtès
2010-05-08 21:28   ` Julian Graham
2010-06-05 22:18     ` Julian Graham
2010-06-12 19:32       ` Julian Graham
2010-06-14 21:34         ` Andy Wingo
2010-06-20 21:23           ` Julian Graham
2010-06-21 18:22             ` Andy Wingo
2010-06-22  3:24               ` Julian Graham
2010-06-22 12:15                 ` Ludovic Courtès [this message]
2010-06-24  3:59                   ` Julian Graham
2010-07-02 13:12                     ` 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=87ocf3l0vv.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).