From: Christopher Howard <christopher@alaskasi.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: SRFIs
Date: Mon, 18 Sep 2017 07:10:52 -0800 [thread overview]
Message-ID: <1505747452.1308.1.camel@alaskasi.com> (raw)
In-Reply-To: <878thcm58s.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1067 bytes --]
Do the SRFIs typically require any C hacking? It seems in Guile there
is usually a C function for each built-in scheme function, but I'm not
sure how that applies to SRFIs.
On Mon, 2017-09-18 at 16:49 +0200, Ludovic Courtès wrote:
> Hello Christopher,
>
> Christopher Howard <christopher.howard@qlfiles.net> skribis:
>
> > Hi, I was just wondering if Guile developers are planning to
> > implement
> > all the SRFIs eventually, or if they are just picking and choosing
> > a
> > few here and there? Put another way, is it just a matter of someone
> > volunteering the time to do each SRFI, or are some not being done
> > on
> > purpose?
>
> I can’t think of any SRFI being purposefully ignored, so I think it’s
> mostly a matter of someone volunteering to do the work.
>
> Ludo’.
>
--
Christopher Howard
Computer Assistant
Alaska Satellite Internet
3239 La Ree Way
Fairbanks, Alaska 99709
1-888-396-5623
https://alaskasatelliteinternet.com
personal web site: https://qlfiles.net
https://emailselfdefense.fsf.org/en/
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2017-09-18 15:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-17 14:49 SRFIs Christopher Howard
2017-09-17 16:04 ` SRFIs Amirouche Boubekki
2017-09-18 14:49 ` SRFIs Ludovic Courtès
2017-09-18 15:10 ` Christopher Howard [this message]
2017-09-18 19:33 ` SRFIs Arne Babenhauserheide
2017-09-18 20:12 ` SRFIs Ludovic Courtès
2017-09-19 20:50 ` SRFIs Taylan Ulrich Bayırlı/Kammer
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=1505747452.1308.1.camel@alaskasi.com \
--to=christopher@alaskasi.com \
--cc=guile-user@gnu.org \
--cc=ludo@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).