From: Mark H Weaver <mhw@netris.org>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: [PATCH] psyntax: custom ellipses using 'with-ellipsis' or R7RS syntax-rules
Date: Thu, 09 Jan 2014 18:07:16 -0500 [thread overview]
Message-ID: <87fvowwy8r.fsf@netris.org> (raw)
In-Reply-To: <87ppo2w5zb.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Wed, 08 Jan 2014 21:53:12 +0100")
ludo@gnu.org (Ludovic Courtès) writes:
> Mark H Weaver <mhw@netris.org> skribis:
>
>> ludo@gnu.org (Ludovic Courtès) writes:
>>
>>> Does something like this work:
>>>
>>> (define-syntax define-inline
>>> (with-ellipsis ---
>>> (syntax-rules ()
>>> ((_ (name parms ---) exp ---)
>>> (define-syntax name
>>> (syntax-rules ()
>>> ((_ args (--- ---))
>>> ((lambda (parms ---) exp ---)
>>> args (--- ---)))))))))
>>
>> No, because as noted in the docs, the custom ellipsis does not propagate
>> to the generated code.
>
> OK, right; it’d work with ‘with-ellipsis’ repeated after the inner
> ‘define-syntax’ I suppose.
Yes.
> Actually my question was more about the ellipsis escaping form
> (... ...). It is affected by ‘with-ellipsis’, right?
Yes, so the following works:
(define-syntax define-inline
(with-ellipsis ---
(syntax-rules ()
((_ (name parms ---) exp ---)
(define-syntax name
(with-ellipsis (--- ---)
(syntax-rules ()
((_ args (--- ---))
((lambda (parms ---) exp ---)
args (--- ---))))))))))
Needless to say, the whole point of custom ellipses is to avoid having
to ever escape ellipses, but you can still do it.
>> Note that as currently implemented, the effect of 'with-ellipsis'
>> also does not propagate into nested syntax definition forms such as
>> 'let-syntax', 'letrec-syntax', and 'define-syntax'. We could go either
>> way on this.
>
> Well, I think it’s fine this way, but then again I’ve been living in
> world without that feature. ;-)
>
> How does R7RS syntax-rules behave in that respect? I guess we should
> just follow suit.
In R7RS, custom ellipsis is not part of the lexical environment, and
thus does not propagate at all. A custom ellipsis affects only the
patterns and templates of the 'syntax-rules' macro it is passed to.
I ended up making the effect of 'with-ellipsis' propagate into syntax
definition forms, since the semantics seem simpler to me.
I pushed this and the 'syntax-error' patch to stable-2.0.
Thanks!
Mark
next prev parent reply other threads:[~2014-01-09 23:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 0:33 [PATCH] psyntax: custom ellipses using 'with-ellipsis' or R7RS syntax-rules Mark H Weaver
2014-01-08 11:41 ` Ludovic Courtès
2014-01-08 20:10 ` Mark H Weaver
2014-01-08 20:53 ` Ludovic Courtès
2014-01-09 23:07 ` Mark H Weaver [this message]
2014-01-10 13:02 ` Ludovic Courtès
2014-01-10 17:08 ` Mark H Weaver
2014-01-10 20:36 ` Ludovic Courtès
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=87fvowwy8r.fsf@netris.org \
--to=mhw@netris.org \
--cc=guile-devel@gnu.org \
--cc=ludo@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).