unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Martin Becze <mjbecze@riseup.net>
Cc: 40371@debbugs.gnu.org, marc.nieper@gmail.com
Subject: bug#40371: [R7RS] Guile does not accept library name parts that are non-negative exact integers
Date: Thu, 23 Nov 2023 09:24:37 -0500	[thread overview]
Message-ID: <87pm007dju.fsf@gmail.com> (raw)
In-Reply-To: <06d43ea8-e13a-6116-a715-04c2d69c12c4@riseup.net> (Martin Becze's message of "Wed, 19 Aug 2020 05:16:57 -0500")

Hello,

Martin Becze <mjbecze@riseup.net> writes:

> Here is a patch that makes things usable for srfi's. (import (srfi
> NNNN)) will work. It just remove the guard condition that was catching
> the Integers. Does anyone know why the guard was there and if it is
> really needed?

Is still still an issue when working with R7RS .sld libraries?  It's
been possible to use e.g. (import (srfi 64)) since commit 2cca09126,
dated September 2019.  This is handled in (ice-9 r6rs-libraries), so not
generally available, but it is in the context of a define-library
definition.

Let us know if the problem is solved on your side, and if so, let's
close this issue!

-- 
Thanks,
Maxim





  parent reply	other threads:[~2023-11-23 14:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-01 10:47 bug#40371: [R7RS] Guile does not accept library name parts that are non-negative exact integers Marc Nieper-Wißkirchen
2020-04-02 19:05 ` Andy Wingo
2020-04-02 19:47   ` Marc Nieper-Wißkirchen
2020-04-02 20:26     ` lloda
2020-04-09  8:29   ` Marc Nieper-Wißkirchen
2020-08-03 20:24 ` Marc Nieper-Wißkirchen
2020-08-19 10:16   ` Martin Becze
2020-08-24 11:41     ` Dr. Arne Babenhauserheide
2023-11-23 14:24     ` Maxim Cournoyer [this message]
2023-11-24  3:45       ` Maxim Cournoyer

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=87pm007dju.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=40371@debbugs.gnu.org \
    --cc=marc.nieper@gmail.com \
    --cc=mjbecze@riseup.net \
    /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).