From: Stephen Compall <s11@member.fsf.org>
Subject: Functions in libguile vs SRFIs
Date: Tue, 15 Jul 2003 17:05:55 -0500 [thread overview]
Message-ID: <200307152205.h6FM5tw30073@csserver.evansville.edu> (raw)
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).
--
Stephen Compall or S11 or sirian
Too many people are thinking of security instead of opportunity. They seem
more afraid of life than death.
-- James F. Byrnes
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next reply other threads:[~2003-07-15 22:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-15 22:05 Stephen Compall [this message]
2003-07-15 22:18 ` Functions in libguile vs SRFIs Nic
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=200307152205.h6FM5tw30073@csserver.evansville.edu \
--to=s11@member.fsf.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).