From: 無無 <yuvallangerontheroad@gmail.com>
To: guile-devel@gnu.org
Subject: A R7RS library name part bug?
Date: Mon, 13 Nov 2023 16:21:28 +0200 [thread overview]
Message-ID: <CABKQn8GrwxvtF3fi5+YPKV6t3gz0c7hB24HUeL_yqSRZVBT68w@mail.gmail.com> (raw)
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.
The files are as follows:
;;; ./a/b/1.scm
(define-library (a b 1)
(import (scheme base))
(export one)
(begin
(define one 'one)))
;;; ./a/b/d-1.scm
(define-library (a b d-1)
(import
(scheme base)
(scheme write)
)
(export
dd-1)
(begin
(define dd-1 'dd-1)))
;;; ./a/b/d.scm
(define-library (a b d)
(import
(scheme base)
(scheme write)
)
(export
dd)
(begin
(define dd 'dd)))
;;; ./a/good-main.scm
(define-library (a c)
(import
(scheme base)
(scheme write)
(a b d)
(a b d-1))
(begin
(display '(a c)) (newline)
(display dd) (newline)
(display dd-1) (newline)))
;;; ./a/bad-main.scm
(define-library (a c)
(import
(scheme base)
(scheme write)
(a b 1))
(begin
(display one) (newline)))
next reply other threads:[~2023-11-13 14:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 14:21 無無 [this message]
2023-11-13 23:17 ` A R7RS library name part bug? Taylan Kammer
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=CABKQn8GrwxvtF3fi5+YPKV6t3gz0c7hB24HUeL_yqSRZVBT68w@mail.gmail.com \
--to=yuvallangerontheroad@gmail.com \
--cc=guile-devel@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).