From: "Marc Nieper-Wißkirchen" <marc.nieper+gnu@gmail.com>
To: "Marc Nieper-Wißkirchen" <marc.nieper+gnu@gmail.com>
Cc: 40252@debbugs.gnu.org
Subject: bug#40252: [R7RS] cond-expand in define-library forms
Date: Mon, 3 Aug 2020 22:23:42 +0200 [thread overview]
Message-ID: <CAEYrNrSPYNBgYQ-p84g=Qej_VZ-=P0Thd9YTBov2yGE8n8jhhA@mail.gmail.com> (raw)
In-Reply-To: <CAEYrNrS3GYnN+UPGe5X1ksy2o6Q_M6=2obrrsSU+43-fP5smkA@mail.gmail.com>
*bump*
Am Fr., 27. März 2020 um 15:17 Uhr schrieb Marc Nieper-Wißkirchen
<marc.nieper+gnu@gmail.com>:
>
> The following valid R7RS library definition is not handled correctly by Guile:
>
> (define-library (guile-test)
> (export fold)
> (cond-expand
> ((library (scheme list))
> (import (scheme list)))
> ((library (srfi srfi-1))
> (import (srfi srfi-1)))))
>
> This is what I get:
>
> $ guile --r7rs -L .
> GNU Guile 3.0.1
> ...
> > (import (guile-test))
> While compiling expression:
> no code for module (scheme list)
> >
>
> Thus, the cond-expand library declaration does not seem to be handled correctly. Other experiments with cond-expand also show strange behaviors:
>
> (define-library (guile-test)
> (export foo)
> (cond-expand
> (guile
> (import (scheme base))))
> (begin
> (define foo 42)))
>
> > (import (guile-test))
> While compiling expression:
> Syntax error:
> unknown location: source expression failed to match any pattern in form (((begin (define foo 42))))
>
> --
>
> Marc
next prev parent reply other threads:[~2020-08-03 20:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-27 14:17 bug#40252: [R7RS] cond-expand in define-library forms Marc Nieper-Wißkirchen
2020-05-07 17:26 ` bug#40252: [PATCH] " Adam Nelson
2020-08-03 20:23 ` Marc Nieper-Wißkirchen [this message]
2021-05-01 20:25 ` bug#40252: Applied Andy Wingo
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='CAEYrNrSPYNBgYQ-p84g=Qej_VZ-=P0Thd9YTBov2yGE8n8jhhA@mail.gmail.com' \
--to=marc.nieper+gnu@gmail.com \
--cc=40252@debbugs.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).