From: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
To: Jean Abou Samra <jean@abou-samra.fr>
Cc: stable.master@unstable.horse, Guile User <guile-user@gnu.org>
Subject: Re: Guile import issue
Date: Thu, 15 Jun 2023 12:25:28 +0000 [thread overview]
Message-ID: <48369eb2-d6e2-7c51-98d3-6626f69cda38@posteo.de> (raw)
In-Reply-To: <50595d2011e433ae65b2cda113e950e8e844a1fd.camel@abou-samra.fr>
On 6/15/23 12:33, Jean Abou Samra wrote:
>
> Le jeudi 15 juin 2023 à 12:29 +0200, Jean Abou Samra a écrit :
>
>> As you can see, the library macro has turned the (export real-part) part into
>> a re-export from (guile).
>>
> Sigh. This is the code from |module/ice-9/r6rs-libraries.scm|:
>
> |(define (compute-exports ifaces specs) (define (re-export? sym) (or-map
> (lambda (iface) (module-variable iface sym)) ifaces)) (define (replace? sym)
> (module-variable the-scm-module sym)) |
>
> This will just treat anything as re-export if it's defined in one of the
> imported modules, even if the module being defined also has a same-named
> binding...
>
Hello Jean!
I should learn how to check these things myself in the Guile sources. Thank you
for that.
This is what I suspected from the behavior I saw.
OK, should I raise this on the Guile developers list?
I can work around it by using define-module in my repo for now. Not mission
critical, although I usually prefer using more "portable" expressions, when I can.
Best regards,
Zelphir
--
repositories:https://notabug.org/ZelphirKaltstahl
prev parent reply other threads:[~2023-06-15 12:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-14 20:15 Guile import issue Zelphir Kaltstahl
2023-06-15 9:59 ` Unstable Horse via General Guile related discussions
2023-06-15 12:27 ` Zelphir Kaltstahl
2023-06-15 10:29 ` Jean Abou Samra
2023-06-15 10:33 ` Jean Abou Samra
2023-06-15 12:25 ` Zelphir Kaltstahl [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=48369eb2-d6e2-7c51-98d3-6626f69cda38@posteo.de \
--to=zelphirkaltstahl@posteo.de \
--cc=guile-user@gnu.org \
--cc=jean@abou-samra.fr \
--cc=stable.master@unstable.horse \
/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).