public inbox for
 help / color / mirror / Atom feed
From: Lassi Kortela <>
To: Helmut Eller <>,
Subject: Re: SRFI inclusion
Date: Sat, 6 Feb 2021 14:48:01 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

> A common interface would be nice, but designing good interfaces is not
> easy.  If somebody comes up with a good interface later, maybe it can be
> added post-hoc; not ideal, but should be doable with a layer of
> indirection.
> What bothers me more, is that maintaining those libraries separately for
> each Scheme system doesn't scale.  It would probably be better to do it
> like they do it for the BOOST libraries.  Have one common code base that
> can be compiled with different compilers; possibly with implementation
> specific versions but maintained as part of the common code base by the
> people who use and care about the libraries.

I agree that the maintenance burden for practical Scheme libraries is 
growing too great for any one person or implementation. We've just been 
having discussions in this general direction on the #scheme IRC channel. 
Several people would like something like the SRFI process, but allowing 
for API evolution, with less stringent requirements to get the API 
design right all at once.

      reply	other threads:[~2021-02-06 12:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-05 16:22 Arvydas Silanskas
2021-02-05 22:03 ` Per Bothner
2021-02-06 10:22   ` Helmut Eller
2021-02-06 12:48     ` Lassi Kortela [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).