From: Sanel Zukan <sanelz@gmail.com>
To: 14449@debbugs.gnu.org
Subject: bug#14449: Guile 2.1 and macro nesting
Date: Thu, 23 May 2013 15:50:32 +0200 [thread overview]
Message-ID: <CAHuZ_ku2bz8+qFDRd1DyrH2yF-wxovdHf7dLWyB-_j=8P=JqTQ@mail.gmail.com> (raw)
Hi,
Looks like macro nesting (using define-macro) inside guile 2.x is no
longer possible. Here is example:
-----------------------------------------
scheme@(guile-user)>
(define-macro (def-caller abbrev proc)
`(define-macro (,abbrev var expr)
`(,',proc
(lambda (,var) ,expr))))
scheme@(guile-user)> (def-caller katch call/cc)
scheme@(guile-user)> (macroexpand '(katch 3 (+ 1 1)))
ice-9/psyntax.scm:2146:53: In procedure #<procedure 282adc0 (args e1
e2)>:
ice-9/psyntax.scm:2146:53: Syntax error:
unknown location: lambda: invalid argument list in subform (3) of (3)
Entering a new prompt. Type `,bt' for a backtrace or `,q' to
continue.
-----------------------------------------
However, doing the same in guile 1.x and/or any other Scheme
implementation where define-macro is native, it works without
problems.
Best,
Sanel
next reply other threads:[~2013-05-23 13:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 13:50 Sanel Zukan [this message]
2013-10-03 9:11 ` bug#14449: Guile 2.1 and macro nesting Ian Price
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='CAHuZ_ku2bz8+qFDRd1DyrH2yF-wxovdHf7dLWyB-_j=8P=JqTQ@mail.gmail.com' \
--to=sanelz@gmail.com \
--cc=14449@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).