unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
To: guile-user@gnu.org
Subject: Use core or SRFIs?
Date: Thu, 24 Oct 2019 17:55:26 +0200	[thread overview]
Message-ID: <9ef7ae59-a2b8-ea06-131c-569512409047@posteo.de> (raw)

Hello Guile Users!

I have a question regarding usage of SRFIs in Guile code.

Sometimes there are core functions, which are also available from an
SRFI implementation. One example I am currently dealing with are bitwise
operations for integer numbers. There is SRFI 60 and there are the core
functions like logand, logior and so on.

Usually I tend to think, that using the SRFI implementation in such
situation is better, as it is an implementation of a common interface,
which other Schemes might also have implemented. Using that makes code
more portable to other Schemes. However, I want to be sure, that this is
a good way of thinking about it. Are there ever arguments against using
an SRFI implementation, when an SRFI implementation provides what I need?

Another example are structs. I usually use SRFI 9 to make some structs,
instead of the core record or struct type.

What do you think?

Best regards,

Zelphir




             reply	other threads:[~2019-10-24 15:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-24 15:55 Zelphir Kaltstahl [this message]
2019-10-24 16:01 ` Use core or SRFIs? Nala Ginrut
2019-10-24 16:41   ` Zelphir Kaltstahl
2019-10-24 17:02   ` John Cowan
2019-10-24 18:26     ` Zelphir Kaltstahl
2019-10-24 18:50       ` John Cowan
2019-10-24 19:47         ` Zelphir Kaltstahl
2019-10-24 19:56           ` John Cowan
2019-10-24 20:18             ` Zelphir Kaltstahl
2019-10-24 17:01 ` Taylan Kammer
2019-10-24 19:48   ` Zelphir Kaltstahl

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=9ef7ae59-a2b8-ea06-131c-569512409047@posteo.de \
    --to=zelphirkaltstahl@posteo.de \
    --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).