From: "Issac Trotts" <ijtrotts@ucdavis.edu>
Subject: Re: Missing Pieces
Date: Thu, 15 Jan 2004 18:02:46 -0800 [thread overview]
Message-ID: <003701c3dbd4$d9130d40$8d8d7880@UCDAVIS.EDU> (raw)
In-Reply-To: Pine.GSO.4.58.0401151641090.20079@marcy.nas.nasa.gov
I've been getting some pretty good mileage out of the r5rs document. You
can find a pdf version with a google search. It's about 50 pages of helpful
stuff, though none of it is specific to guile.
Issac
----- Original Message -----
From: "Brian S McQueen" <bqueen@nas.nasa.gov>
To: <guile-user@gnu.org>
Sent: Thursday, January 15, 2004 4:52 PM
Subject: Missing Pieces
> Somehow I am missing out on a lot of information about guile. For
> instance, as I browsed some old email list today I see there is a function
> c-string, mentioned as though it were common knowledge and part of some
> familiar library. How are new-comers to guile going to learn about all
> the great things you all have produced. Just yesterday I found out about
> this: (help cons*). A built-in help feature and I didn't even know about
> it. I have been reading the headers for libguile, poking around in the
> srfi and ice-9 scheme directories, but that is not enough. I have read
> the guile web pages many times by now. Does anyone have any suggestions
> to helping out new-comers to guile? I guess what is needed is a book like
> the old Perl 4 book where all the nooks and crannys of Perl were laid
> bare - one of those O'Reilly type books.
>
> Brian
>
>
> _______________________________________________
> 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
prev parent reply other threads:[~2004-01-16 2:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-16 0:52 Missing Pieces Brian S McQueen
2004-01-16 2:02 ` Issac Trotts [this message]
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='003701c3dbd4$d9130d40$8d8d7880@UCDAVIS.EDU' \
--to=ijtrotts@ucdavis.edu \
/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).