From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: [PATCH] psyntax: custom ellipses using 'with-ellipsis' or R7RS syntax-rules
Date: Wed, 08 Jan 2014 12:41:06 +0100 [thread overview]
Message-ID: <871u0i8zvx.fsf@gnu.org> (raw)
In-Reply-To: 87bo0del31.fsf@netris.org
Hi, Mark,
Mark H Weaver <mhw@netris.org> skribis:
> In the end, here's how this works: 'with-ellipsis' binds a special
> identifier named #{ $sc-ellipsis }# using a new 'ellipsis' binding type.
> The new ellipsis identifier is stored within the binding. In order to
> determine whether an identifier X is an ellipsis, the binding for
> #{ $sc-ellipsis }# is looked up in the lexical environment of X. If the
> binding is found and has binding-type 'ellipsis', then X is compared to
> the identifier stored in the binding using 'bound-id=?'. Otherwise, X
> is compared to '...' using 'free-id=?' as was done before.
This looks nice! Thanks for providing the detailed reasoning, that’s
insightful.
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 (--- ---)))))))))
Looks good to me for 2.0.
Could you wrap lines to 80 columns in psyntax.scm?
> +@subsubsection Specifying a custom ellipsis identifier
Should be “Specifying a Custom Ellipsis Identifier”.
> +@subsubsection Custom ellipsis identifiers for syntax-case macros
Likewise.
> + (define-syntax define-quotation-macros
> + (lambda (x)
> + (syntax-case x ()
> + ((_ (macro-name head-symbol) ...)
> + #'(begin (define-syntax macro-name
> + (lambda (x)
> + (with-ellipsis …
> + (syntax-case x ()
> + ((_ x …)
> + #'(quote (head-symbol x …)))))))
> + ...)))))
Pretty cool. :-)
Thanks,
Ludo’.
next prev parent reply other threads:[~2014-01-08 11:41 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 [this message]
2014-01-08 20:10 ` Mark H Weaver
2014-01-08 20:53 ` Ludovic Courtès
2014-01-09 23:07 ` Mark H Weaver
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=871u0i8zvx.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@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).