From: Sam Lee via "Bug reports for GUILE, GNU's Ubiquitous Extension Language" <bug-guile@gnu.org>
To: "Linus Björnstam" <linus.bjornstam@veryfast.biz>
Cc: 52218@debbugs.gnu.org
Subject: bug#52218: Unable to define more than one R7RS library per file
Date: Thu, 2 Dec 2021 02:55:33 +0000 [thread overview]
Message-ID: <20211202025533.as5notbwgncsyb2v@localhost> (raw)
In-Reply-To: <aebc490c-621c-4e2a-b232-19c0809e1f59@www.fastmail.com>
On 2021-12-01 11:00 +0100, Linus Björnstam wrote:
> This is in line with the limitations of guile's R6RS implementation. I
> think this is a long standing, low priority bug. It has to do with the
> expansion of library (or define-library in this case) not properly
> resetting the current module.
>
> In the manual there is a section called "R6RS incompatibilities" that
> mentions this. Maybe an "R7RS incompatibilities" should be added.
Hi Linus,
There already exist a page in the manual about "Incompatibilities with
the R7RS" [1]. Perhaps a paragraph similar to that found in the R6RS
incompatibilities page should be added to the R7RS incompatibilities
page. Something like this:
"Multiple @code{define-library} forms in one file are not yet supported.
This is because the expansion of @code{define-library} sets the current
module, but does not restore it. This is a bug."
[1]: https://www.gnu.org/software/guile/manual/html_node/R7RS-Incompatibilities.html
next prev parent reply other threads:[~2021-12-02 2:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211201074553.bzuoffwpaxw3da44.ref@localhost>
2021-12-01 7:45 ` bug#52218: Unable to define more than one R7RS library per file Sam Lee via Bug reports for GUILE, GNU's Ubiquitous Extension Language
2021-12-01 10:00 ` Linus Björnstam
2021-12-02 2:55 ` Sam Lee via Bug reports for GUILE, GNU's Ubiquitous Extension Language [this message]
2021-12-03 14:20 ` Linus Björnstam
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=20211202025533.as5notbwgncsyb2v@localhost \
--to=bug-guile@gnu.org \
--cc=52218@debbugs.gnu.org \
--cc=linus.bjornstam@veryfast.biz \
--cc=samlee746@yahoo.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).