From: Noah Lavine <noah.b.lavine@gmail.com>
To: guile-devel <guile-devel@gnu.org>
Subject: Do you recognize these modules?
Date: Tue, 1 May 2012 18:26:28 -0400 [thread overview]
Message-ID: <CA+U71=PFmSv2vJaya_P6jCagWKidEVEQraj5LRsXCZWQwSN81A@mail.gmail.com> (raw)
Hello all,
I was inspired by a recent post about (ice-9 occam-channel) to take a
look and see what modules don't have documentation. I've only looked
at the (ice-9 ...) modules so far, but there are a lot of them. (I
checked for documentation by going to the top-level info node for
Guile documentation in Emacs and searching the manual for any mention
of the module.)
I am happy to add documentation for some of these modules, but I'd
like to ask first to see if anyone on this list knows what they do. I
think this is also the time to ask if we want to remove some of these
modules instead of documenting them (especially (ice-9 lineio)). One
nice thing I learned in this project is that Guile has a lot of cool
data structures and algorithms built in. I think it would be great if
they were discoverable too.
Here are some notes I made as I went through ice-9/*.scm. Does anyone
know anything about these modules?
(ice-9 and-let-star) not documented (but also available as srfi-2?)
(ice-9 binary-ports) not really documented except by brief mention
under "R6RS I/O Ports"
(ice-9 calling) not documented at all.
(ice-9 channel) not documented at all.
(ice-9 command-line) not documented at all.
(ice-9 common-list) not documented at all.
(ice-9 control): shift* and reset* need documentation.
(ice-9 documentation) not documented at all.
(ice-9 expect): all but expect and expect-strings need documentation.
(ice-9 gap-buffer) not documented at all. is this module related to
Elisp support?
(ice-9 hcons) not documented at all.
(ice-9 lineio) not documented at all. but a comment in that module
says that it should be removed eventually. maybe the time is now?
(ice-9 list) not documented at all.
(ice-9 ls) not documented at all.
(ice-9 mapping) not documented at all.
(ice-9 match): everything except match needs documentation.
(ice-9 null) not documented at all. but maybe it's not supposed to be.
(ice-9 occam-channel) not documented at all.
(ice-9 poe) not documented at all.
(ice-9 poll) not documented at all.
(ice-9 popen): port/pid-table needs documentation.
(ice-9 runq): not documented at all.
(ice-9 safe-r5rs): not documented at all.
(ice-9 safe): not documented at all.
(ice-9 save-stack): not documented at all.
(ice-9 scm-style-repl): not documented at all.
(ice-9 serialize): not documented at all.
(ice-9 session): not documented at all.
(ice-9 stack-catch): not documented at all.
(ice-9 string-fun): not documented at all.
(ice-9 threads): the *par* procedures need documentation.
(ice-9 time): not documented at all.
(ice-9 top-repl): not documented at all.
(ice-9 weak-vector): not documented at all.
Thanks,
Noah
next reply other threads:[~2012-05-01 22:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-01 22:26 Noah Lavine [this message]
2012-05-01 23:22 ` Do you recognize these modules? Thien-Thi Nguyen
2012-05-02 15:26 ` Noah Lavine
2012-05-14 8:04 ` Thien-Thi Nguyen
2012-05-14 10:52 ` Noah Lavine
2012-05-14 12:59 ` David Kastrup
2012-05-14 13:59 ` Noah Lavine
2012-05-14 14:12 ` David Kastrup
2012-05-14 12:44 ` Ludovic Courtès
2012-05-14 17:00 ` Thien-Thi Nguyen
2012-05-14 17:30 ` Noah Lavine
2012-05-15 20:14 ` Andy Wingo
2012-05-25 8:53 ` Thien-Thi Nguyen
2012-05-25 12:48 ` Andy Wingo
2012-05-25 17:02 ` Thien-Thi Nguyen
2012-07-11 3:02 ` Noah Lavine
2012-07-11 7:21 ` Thien-Thi Nguyen
2012-07-11 10:44 ` Andy Wingo
2012-07-11 15:20 ` Noah Lavine
2012-07-11 17:59 ` Noah Lavine
2012-08-25 22:27 ` Noah Lavine
2012-08-26 20:47 ` Ludovic Courtès
2013-03-23 10:36 ` Thien-Thi Nguyen
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='CA+U71=PFmSv2vJaya_P6jCagWKidEVEQraj5LRsXCZWQwSN81A@mail.gmail.com' \
--to=noah.b.lavine@gmail.com \
--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).