From: Taylan Kammer <taylan.kammer@gmail.com>
To: 無無 <yuvallangerontheroad@gmail.com>, guile-devel@gnu.org
Subject: Re: A R7RS library name part bug?
Date: Tue, 14 Nov 2023 00:17:44 +0100 [thread overview]
Message-ID: <b79f7b94-45d6-4b46-b876-cf43a67bb214@gmail.com> (raw)
In-Reply-To: <CABKQn8GrwxvtF3fi5+YPKV6t3gz0c7hB24HUeL_yqSRZVBT68w@mail.gmail.com>
On 13.11.2023 15:21, 無無 wrote:
> I have read that in R7RS a library name is defined as:
>
> <library name> -> ( <library name part>+ )
> <library name part> -> <identifier> | <uinteger 10>
> <uinteger R> -> <digit R>
> <digit 10> -> <digit>
> <digit> -> 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9
>
> That means that a valid library name would be something like (a b 1),
> where "1" is a valid library name part, but the following code
> disagrees. running `guile --r7rs -L . a/good-main.scm` works while
> `guile --r7rs -L . a/bad-main.scm` fails.
>
> [...]
>
This is unfortunately a known limitation in Guile's R7RS support.
IIRC, integers in library names only works for (srfi N) which is
internally transformed to (srfi srfi-N).
--
Taylan
prev parent reply other threads:[~2023-11-13 23:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 14:21 A R7RS library name part bug? 無無
2023-11-13 23:17 ` Taylan Kammer [this message]
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=b79f7b94-45d6-4b46-b876-cf43a67bb214@gmail.com \
--to=taylan.kammer@gmail.com \
--cc=guile-devel@gnu.org \
--cc=yuvallangerontheroad@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).