From: Nic <nferrier@tapsellferrier.co.uk>
Cc: guile-user@gnu.org
Subject: Re: Functions in libguile vs SRFIs
Date: 15 Jul 2003 23:18:57 +0100 [thread overview]
Message-ID: <87u19nzb5a.fsf@tapsellferrier.co.uk> (raw)
In-Reply-To: <200307152205.h6FM5tw30073@csserver.evansville.edu>
Stephen Compall <s11@member.fsf.org> writes:
> On the functions now duplicated (some with slight enhancements)
> between libguile and the SRFIs:
>
> Are the ones in libguile (going to be) deprecated? If not, are the
> SRFI versions preferred? If not, IMHO, they should be, for the sake
> of modularity (not to mention standards).
On this note: is the guile team interested in getting documentation
patches which merge the doc of srfi's into the body of the doc?
For example: the section on Compound-Types/Lists includes all the
srfi-1 functions.
I'd be happy to do the occasional documentation patch on this basis.
Nic Ferrier
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2003-07-15 22:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-15 22:05 Functions in libguile vs SRFIs Stephen Compall
2003-07-15 22:18 ` Nic [this message]
2003-07-17 22:39 ` 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=87u19nzb5a.fsf@tapsellferrier.co.uk \
--to=nferrier@tapsellferrier.co.uk \
--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).