From: David Kastrup <dak@gnu.org>
To: 17096@debbugs.gnu.org
Subject: bug#17096: Guile 1.8: syntax-case messed up when "void" is defined
Date: Wed, 26 Mar 2014 12:51:38 +0100 [thread overview]
Message-ID: <87mwgdtbxx.fsf@fencepost.gnu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 37 bytes --]
When running the following program
[-- Attachment #2: baba.scm --]
[-- Type: text/plain, Size: 136 bytes --]
(define void 6)
(use-modules (ice-9 syncase))
(define-syntax absurd
(lambda (x)
(syntax-case x ()
((_ var) (syntax var)))))
[-- Attachment #3: Type: text/plain, Size: 446 bytes --]
through Guile 1.8, I get the error
ERROR: Wrong type to apply: 6
The same appears to go through without problem (apart from the
deprecation warning for the module) on Guile 2.0.
Is there any workaround? Apart from the obvious "don't define void"
which is not a good option for the actual application at hand since the
function is part of a user-level API. And it's not like "void" is
documented as being anything here...
--
David Kastrup
next reply other threads:[~2014-03-26 11:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-26 11:51 David Kastrup [this message]
2014-04-01 6:38 ` bug#17096: Guile 1.8: syntax-case messed up when "void" is defined Mark H Weaver
2014-04-01 9:03 ` David Kastrup
2014-04-01 13:44 ` Mark H Weaver
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=87mwgdtbxx.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--cc=17096@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).