From: Taylan Kammer <taylan.kammer@gmail.com>
To: guile-devel@gnu.org
Subject: Re: cond-expand-provide and (scheme base)
Date: Fri, 23 Oct 2020 04:57:12 +0200 [thread overview]
Message-ID: <710e78e9-daeb-511e-b230-248cc3d77fdb@gmail.com> (raw)
In-Reply-To: <87k0viunj3.fsf@gmail.com>
On 22.10.2020 20:24, Taylan Kammer wrote:
> I think the following discrepancy should probably be fixed:
>
> $ guile -L ~/src/scheme/bytestructures/
> guile> ,use (scheme eval)
> guile> (eval '(cond-expand (lp64 #t) (else #f))
> (environment '(guile) ; <=== DIFFERENCE HERE
> '(bytestructures guile numeric-data-model)))
> $1 = #t
> guile> (eval '(cond-expand (lp64 #t) (else #f))
> (environment '(scheme base) ; <=== DIFFERENCE HERE
> '(bytestructures guile numeric-data-model)))
> $2 = #f
To clarify:
The module (bytestructures guile numeric-data-model) provides the 'lp64'
condition via 'cond-expand-provide'.
The 'cond-expand' imported from the (guile) module correctly sees this,
but the one imported from (scheme base) seems to ignore it.
Taylan
prev parent reply other threads:[~2020-10-23 2:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 18:24 cond-expand-provide and (scheme base) Taylan Kammer
2020-10-23 2:57 ` 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=710e78e9-daeb-511e-b230-248cc3d77fdb@gmail.com \
--to=taylan.kammer@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).