From: Andy Wingo <wingo@pobox.com>
To: Nala Ginrut <nalaginrut@gmail.com>
Cc: 20546@debbugs.gnu.org
Subject: bug#20546: Syntax bug in master branch (till d99fedc5fd38c0)
Date: Thu, 23 Jun 2016 22:27:11 +0200 [thread overview]
Message-ID: <87eg7nlkgw.fsf@pobox.com> (raw)
In-Reply-To: <1431340166.3009.100.camel@Renee-desktop.suse> (Nala Ginrut's message of "Mon, 11 May 2015 18:29:26 +0800")
On Mon 11 May 2015 12:29, Nala Ginrut <nalaginrut@gmail.com> writes:
> I'm using master branch (till d99fedc5fd38c0), and I found this code
> can't run in 2.1, but works in 2.0:
>
> (define-syntax define-art
> (lambda (x)
> (syntax-case x ()
> ((_ name) (identifier? #'name)
> #`(begin
> (define name 2)
> (define #,(datum->syntax #'name
> (symbol-append 'define- (syntax->datum #'name)))
> 33))))))
>
> Of course, the meaning of this code is trivial.
Works for me:
wingo@clucks:~/src/guile$ meta/guile
GNU Guile 2.1.3.17-b8f5c-dirty
Copyright (C) 1995-2016 Free Software Foundation, Inc.
Guile comes with ABSOLUTELY NO WARRANTY; for details type `,show w'.
This program is free software, and you are welcome to redistribute it
under certain conditions; type `,show c' for details.
Enter `,help' for help.
scheme@(guile-user)> (define-syntax define-art
... (lambda (x)
... (syntax-case x ()
... ((_ name) (identifier? #'name)
... #`(begin
... (define name 2)
... (define #,(datum->syntax #'name
... (symbol-append 'define- (syntax->datum #'name)))
... 33))))
... )
... )
scheme@(guile-user)> (define-art foo)
scheme@(guile-user)> foo
$1 = 2
scheme@(guile-user)> define-foo
$2 = 33
Must be some bug that was fixed in the meantime?
next prev parent reply other threads:[~2016-06-23 20:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 10:29 bug#20546: Syntax bug in master branch (till d99fedc5fd38c0) Nala Ginrut
2016-06-23 20:27 ` Andy Wingo [this message]
2016-08-07 10:32 ` 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=87eg7nlkgw.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=20546@debbugs.gnu.org \
--cc=nalaginrut@gmail.com \
/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).