From: Andy Wingo <wingo@igalia.com>
To: "Marc Nieper-Wißkirchen" <marc.nieper@gmail.com>
Cc: 40371@debbugs.gnu.org
Subject: bug#40371: [R7RS] Guile does not accept library name parts that are non-negative exact integers
Date: Thu, 02 Apr 2020 21:05:37 +0200 [thread overview]
Message-ID: <87369lg132.fsf@igalia.com> (raw)
In-Reply-To: <CAEYrNrSU-vLLziE_2mVPzkk5cOHii+2SF-1okvHn=TUjBHjwkw@mail.gmail.com> ("Marc \=\?utf-8\?Q\?Nieper-Wi\=C3\=9Fkirchen\=22's\?\= message of "Wed, 1 Apr 2020 12:47:12 +0200")
In the concrete case of the SRFI modules, importing e.g. (srfi 9) works
AFAIU. Does this not work for you?
I think that allowing numbers as module name components, beyond the SRFI
modules, is not currently a good idea for Guile. I had a look at it and
it's a bit too intrusive.
Andy
On Wed 01 Apr 2020 12:47, Marc Nieper-Wißkirchen <marc.nieper@gmail.com> writes:
> An R7RS library name consists of parts, where each part is either a symbol or
> a non-negative exact integer. Guile doesn't support the latter ones.
>
> This is unfortunate as the implementation of a SRFI NNN is usually delivered
> in form of a library named (srfi NNN).
>
> When this is corrected, for interoperability, it would be great if Guile offers
> the included SRFIs not only under the name (srfi srfi-NNN) but also under
> (srfi NNN).
>
> Thanks,
>
> Marc
next prev parent reply other threads:[~2020-04-02 19:05 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 [this message]
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
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=87369lg132.fsf@igalia.com \
--to=wingo@igalia.com \
--cc=40371@debbugs.gnu.org \
--cc=marc.nieper@gmail.com \
/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).