From: Han-Wen Nienhuys <hanwen@cs.uu.nl>
Cc: guile-devel@gnu.org
Subject: doco srfi-1 iota
Date: Tue, 8 Jul 2003 01:16:52 +0200 [thread overview]
Message-ID: <16137.65380.115639.994664@localhost.localdomain> (raw)
In-Reply-To: <871xx2ov97.fsf@zip.com.au>
user42@zip.com.au writes:
> * srfi-modules.texi (SRFI-1 Constructors): In iota, reword a bit for
> clarity and add a couple of examples.
>
> I found the formula for each element less clear than it could be, and
> thought a couple of examples would be enough to illustrate what
> happens.
In general, I wonder why the SRFI documentation doesn't have much
examples. In some cases, the text of the SRFI itself is more clear.
which begs the question, why aren't the SRFIs themselves used as
documentation?
--
Han-Wen Nienhuys | hanwen@cs.uu.nl | http://www.xs4all.nl/~hanwen
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-07-07 23:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-07 21:57 doco srfi-1 iota Kevin Ryde
2003-07-07 23:16 ` Han-Wen Nienhuys [this message]
2003-07-11 22:43 ` Kevin Ryde
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=16137.65380.115639.994664@localhost.localdomain \
--to=hanwen@cs.uu.nl \
--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).