From: rm@fabula.de
Cc: guile-user@gnu.org
Subject: Re: Around again, and docs lead role
Date: Sat, 3 May 2003 13:34:03 +0200 [thread overview]
Message-ID: <20030503113403.GC5407@www> (raw)
In-Reply-To: <m3y91oabir.fsf@latakia.dyndns.org>
On Fri, May 02, 2003 at 10:40:12PM -0600, Robert Uhl wrote:
> Ricard Mira <ricardmm@tiscali.es> writes:
> >
> > IMHO, the overall organization of the documentation isn't clear.
>
> My own problem has been a feeling that it's not complete. At least,
> trying to figure out the C bindings has been...interesting.
I had similar experiences. The existing documentation *is* very good,
but i was astonished to find a few undocumentes jewels (well, actually
pretty neccessary stuff:) in the header files ...
I started writing up some info last night but i'm not shure whether
the lack of documentation actually manifests some public vs. private
API issue.
> But other
> than that it's been decent. Of course, I did have to learn Scheme from
> SICP; it'd be nice were there an intro to Scheme itself somewhere.
Hmm, there a a handfull of pretty good Scheme intros available, why
bother duplicating these efforts (better: write a Guile-specific addendum
for one of these).
>
> > Also, I believe that "Part V: Guile Modules" should disappear, because
> > features should be documented according to their functionality, not
> > according to their origin or implementation (SLIB, SRFIs, etc.).
>
> OTOH, it's nice to know what's part of guile itself and what's not, at
> least to some of us. Could go either way, I guess.
Yes. And it would be _very_ helpfull if the documentation would mention
what modules need to be "used" for certain functions [(ice-9 regexp) for
regular expressions ...).
Another question: there's some very good information in the guile-workbook
CVS module. But sometimes it's hard to tell whether a piece is documenting
an existing fact of Guile or rather proposing a new impementation.
Ralf Mattes
>
> --
> Robert Uhl <ruhl@4dv.net>
> Xristus usstôþ! Sunjaba usstôþ!
>
>
> _______________________________________________
> Guile-user mailing list
> Guile-user@gnu.org
> http://mail.gnu.org/mailman/listinfo/guile-user
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2003-05-03 11:34 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-26 7:33 Around again, and docs lead role Neil Jerram
2003-04-26 10:19 ` Thamer Al-Harbash
2003-04-27 20:56 ` Neil Jerram
[not found] ` <3E92E1B40021F4D7@pop3.tiscalinet.es>
2003-04-27 21:01 ` Neil Jerram
[not found] ` <3E92E1B4002B0632@pop3.tiscalinet.es>
2003-04-30 22:47 ` Neil Jerram
[not found] ` <3EAFE4EC000D9733@pop1.tiscalinet.es>
2003-05-07 21:06 ` Doc organization (Re: Around again, and docs lead role) Neil Jerram
2003-05-08 16:21 ` Rob Browning
2003-05-08 17:50 ` rm
2003-05-08 22:47 ` Neil Jerram
2003-10-28 16:09 ` Thien-Thi Nguyen
2003-05-08 22:36 ` Neil Jerram
2003-05-09 2:23 ` Rob Browning
2003-05-09 17:46 ` David Van Horn
2003-05-10 11:32 ` Neil Jerram
2003-05-15 16:02 ` Rob Browning
2003-05-15 16:33 ` Paul Jarc
2003-05-09 11:52 ` Bill Schottstaedt
2003-05-13 23:01 ` Neil Jerram
2003-05-14 1:07 ` Viktor Pavlenko
2003-05-14 14:29 ` Bill Schottstaedt
2003-05-15 7:55 ` Mikael Djurfeldt
2003-05-17 3:02 ` Max Techter
2003-05-09 8:15 ` tomas
2003-05-10 12:01 ` Neil Jerram
2003-05-12 11:40 ` tomas
2003-05-03 4:40 ` Around again, and docs lead role Robert Uhl
2003-05-03 11:34 ` rm [this message]
2003-05-03 22:21 ` Robert Uhl
2003-05-03 23:15 ` Thamer Al-Harbash
2003-05-04 8:40 ` David Allouche
2003-05-04 21:34 ` Robert Uhl
2003-05-04 19:47 ` rm
2003-05-04 21:42 ` Robert Uhl
2003-05-04 23:38 ` Thien-Thi Nguyen
2003-05-07 22:52 ` Neil Jerram
2003-05-08 22:32 ` State of Docs [was] " rm
2003-05-08 23:11 ` Neil Jerram
2003-05-10 0:47 ` State of Docs 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=20030503113403.GC5407@www \
--to=rm@fabula.de \
--cc=guile-user@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).