public inbox for
 help / color / mirror / Atom feed
From: Helmut Eller <>
Subject: Re: SRFI inclusion
Date: Sat, 06 Feb 2021 11:22:40 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Fri, Feb 05 2021, Per Bothner wrote:

> At least there are some semi-standard naming conventions, but I think
> this approach of defining dozens of distinctly-named functions for
> each datatype is a dead end.)

I don't think that this is a problem, because the module system keeps
those functions in their own namespace and shouldn't bother people who
don't use them.

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

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.


  reply	other threads:[~2021-02-06 10:22 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 [this message]
2021-02-06 12:48     ` Lassi Kortela

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