From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: rfc: (ice-9 accumulate)
Date: Mon, 11 Jan 2010 14:21:15 +0100 [thread overview]
Message-ID: <87eilweq0k.fsf@gnu.org> (raw)
In-Reply-To: 8763799nwr.fsf@ambire.localdomain
Hello,
Thien-Thi Nguyen <ttn@gnuvola.org> writes:
> There's lots of stuff in ice-9 that noone knows about, but I don't
> think there's something like this. Hopefully we can document more of
> it using the new (texinfo reflection) infrastructure.
>
> In reply to a similar comment from Ludovic, i offered to submit patches
> for missing (ice-9 foo) documentation. I hereby revise that offer to
> submit patches using this infrastructure, once i get around to playing
> with it. I imagine it can't be much different from Guile 1.4.x's.
I’d prefer if it were used only for non-ice-9 modules. I really
sympathize with what the GCS says (info "(standards) Doc Strings and
Manuals"):
Some programming systems, such as Emacs, provide a documentation
string for each function, command or variable. You may be tempted to
write a reference manual by compiling the documentation strings and
writing a little additional text to go around them--but you must not
do it. That approach is a fundamental mistake. The text of
well-written documentation strings will be entirely wrong for a
manual.
Thanks,
Ludo’.
next prev parent reply other threads:[~2010-01-11 13:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-09 10:44 rfc: (ice-9 accumulate) Thien-Thi Nguyen
2010-01-09 21:55 ` Andy Wingo
2010-01-11 6:05 ` Thien-Thi Nguyen
2010-01-11 13:21 ` Ludovic Courtès [this message]
2010-01-11 14:16 ` Thien-Thi Nguyen
2010-01-11 20:57 ` Andy Wingo
2010-01-11 0:48 ` Ludovic Courtès
2010-01-11 5:51 ` Thien-Thi Nguyen
2010-01-11 13:26 ` Ludovic Courtès
2010-01-11 14:34 ` Thien-Thi Nguyen
2010-01-11 20:51 ` Andy Wingo
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=87eilweq0k.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).