From: Stefan Israelsson Tampe <stefan.itampe@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guile-devel@gnu.org
Subject: Re: Enhancement to the syntax system?
Date: Tue, 3 Jul 2012 16:37:14 +0200 [thread overview]
Message-ID: <CAGua6m1z_Te5gi6pmQBJ_Xf-8DpURfjQMgp=vPbryuZcbJsC8A@mail.gmail.com> (raw)
In-Reply-To: <87r4stss4d.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1402 bytes --]
On Tue, Jul 3, 2012 at 12:41 AM, Ludovic Courtès <ludo@gnu.org> wrote:
> Hey!
>
> Stefan Israelsson Tampe <stefan.itampe@gmail.com> skribis:
>
> > Maybe this help to see what I'm after,
> >
> > #'(let ((x v)) #.(f #'x))
> >
> > <=>
> >
> > (let-syntax ((g (lambda (stx) (syntax-case stx ((_ x) (f #'x)))))
> > #'(let ((x v)) (g x))
>
> Sorry, I fail to understand the problem you’re trying to solve.
>
> Hmm The #' probably need to be moved to the left of the expression and
there might be problems with phases in this analogy but I guess you saw
that I wanted to spin the function f on a syntax argument that contained
the binding of x done in the let which is not the case If you do a simple #,
The above idiom is not frequent to the point that special syntax is
> needed, is it?
>
>
If you want to code your macros like Alex does in ice-9/match.scm then it's
not a problem.
If you want to try another path using functions in stead of macros and
working hard with #, and #,@
you will for complex macros like a matcher need to gensym by hand or
destroy the readability of the
code. As illustrated by the simple example above. It's not that a
devastating issue because I have coded quite a lot of CL macros before and
can cope with gensymming, but I find it frustrating to know that there
probably exists a better way.
> Thanks,
> Ludo’.
>
/Stefan
[-- Attachment #2: Type: text/html, Size: 2168 bytes --]
next prev parent reply other threads:[~2012-07-03 14:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-30 15:22 Enhancement to the syntax system? Stefan Israelsson Tampe
2012-07-02 19:28 ` Ludovic Courtès
2012-07-02 20:43 ` Stefan Israelsson Tampe
2012-07-02 22:41 ` Ludovic Courtès
2012-07-03 14:37 ` Stefan Israelsson Tampe [this message]
2012-07-03 21:33 ` Ludovic Courtès
2012-07-03 21:52 ` Stefan Israelsson Tampe
2012-07-04 7:47 ` Marijn
2012-07-04 8:04 ` Stefan Israelsson Tampe
2012-07-09 15:52 ` Ludovic Courtès
2012-07-09 17:40 ` Stefan Israelsson Tampe
2012-07-10 8:24 ` Ludovic Courtès
2012-07-10 13:35 ` Stefan Israelsson Tampe
2012-07-10 14:34 ` Marijn
2012-07-10 14:51 ` [racket-dev] " Eli Barzilay
[not found] ` <20476.16781.257276.194149-a5nvgYPMCZcx/1z6v04GWfZ8FUJU4vz8@public.gmane.org>
2012-07-10 15:03 ` Matthew Flatt
2012-07-10 15:26 ` [racket-dev] " Ludovic Courtès
2012-07-10 15:44 ` Stefan Israelsson Tampe
2012-07-10 17:47 ` Stefan Israelsson Tampe
2012-07-10 16:48 ` Eli Barzilay
2014-05-03 21:29 ` Marijn Schouten (hkBst)
2012-07-10 15:44 ` Ryan Culpepper
2012-07-10 15:22 ` Ludovic Courtès
2012-07-10 7:36 ` Stefan Israelsson Tampe
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='CAGua6m1z_Te5gi6pmQBJ_Xf-8DpURfjQMgp=vPbryuZcbJsC8A@mail.gmail.com' \
--to=stefan.itampe@gmail.com \
--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).