unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
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: Mon, 24 Aug 2020 13:41:45 +0200	[thread overview]
Message-ID: <87eenwxocm.fsf@web.de> (raw)
In-Reply-To: <06d43ea8-e13a-6116-a715-04c2d69c12c4@riseup.net>

[-- Attachment #1: Type: text/plain, Size: 567 bytes --]


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?

Thank you for the patch!

I would like to argue in favor of supporting this. It is currently the
only reason why Guile has to use the r6rs testsuite for srfi-197 instead
of the r7rs testsuite.

Best wishes,
Arne
-- 
Unpolitisch sein
heißt politisch sein
ohne es zu merken

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1076 bytes --]

  reply	other threads:[~2020-08-24 11:41 UTC|newest]

Thread overview: 11+ 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 [this message]
2023-11-23 14:24     ` Maxim Cournoyer
2023-11-24  3:45       ` Maxim Cournoyer
2024-08-21  7:44 ` bug#40371: [R7RS] Guile does not accept library name parts that, " Retropikzel via Bug reports for GUILE, GNU's Ubiquitous Extension Language

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=87eenwxocm.fsf@web.de \
    --to=arne_bab@web.de \
    --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).