From: Mark H Weaver <mhw@netris.org>
To: marco.maggi-ipsu@poste.it
Cc: 13509-done@debbugs.gnu.org
Subject: bug#13509: wrong "definition in expression context" in R6RS mode
Date: Thu, 31 Jan 2013 01:10:07 -0500 [thread overview]
Message-ID: <874nhxj328.fsf@tines.lan> (raw)
In-Reply-To: <87obgjfxy8.fsf@rapitore.luna> (Marco Maggi's message of "Sun, 20 Jan 2013 20:37:03 +0100")
Marco Maggi <marco.maggi-ipsu@poste.it> writes:
> #!r6rs
> (import (rnrs))
> (define (alpha)
> (define-syntax define-special
> (syntax-rules ()
> ((_ ?who ?val)
> (define ?who ?val))))
> (define-special beta #t)
> #f)
> (alpha)
>
> should succeed, but instead it fails with:
>
[...]
> ;;; /home/marco/var/tmp/proof.sps:12:2: definition in
> ;;; expression context, where definitions a re not allowed, in form (define beta #t)
Fixed in ceb7f9cc126f50e0cc8956b80ac5d111580b23c8
(which is now in stable-2.0 but not yet in master)
Thanks for the report!
Mark
prev parent reply other threads:[~2013-01-31 6:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-20 19:37 bug#13509: wrong "definition in expression context" in R6RS mode Marco Maggi
2013-01-23 23:48 ` Mark H Weaver
2013-01-31 6:10 ` Mark H Weaver [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=874nhxj328.fsf@tines.lan \
--to=mhw@netris.org \
--cc=13509-done@debbugs.gnu.org \
--cc=marco.maggi-ipsu@poste.it \
/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).