From: Ian Price <ianprice90@googlemail.com>
To: Panicz Maciej Godek <godek.maciek@gmail.com>
Cc: "guile-user@gnu.org" <guile-user@gnu.org>
Subject: Re: and-let* is not composable?
Date: Sat, 05 Oct 2013 09:00:48 +0100 [thread overview]
Message-ID: <87fvsgcfkf.fsf@Kagami.home> (raw)
In-Reply-To: <CAMFYt2boCYdC9ntfFuN2ZbgZAqzBVZZPj7W_66-b+W9m5x=fwQ@mail.gmail.com> (Panicz Maciej Godek's message of "Sat, 5 Oct 2013 00:27:27 +0200")
Panicz Maciej Godek <godek.maciek@gmail.com> writes:
> presentation of Racket macro
> system, http://www.infoq.com/presentations/racket,
> where he points to a quite good introduction to "define-syntax" macros
> by Greg Hendershott: http://www.greghendershott.com/fear-of-macros/
I was also made aware of it recently, it seems like a fine introduction,
and I had even considered mentioning it to you in this thread :) but...
> And now that my head is clearer on this regard, I think it is
> confusing
> to call them "syntax-case" macros, because "syntax-case" is rather
> auxiliary than essential for defining that sort of macro.
(This is mostly true, but it's been a conventional name for some 20 years :/)
> So I believe that at least placing a link to than explanation in the
> manual
> could be a great help for beginners.
... the problem is it makes a lot of references to Racket, and Racket
specific ways of doing things. Much of it can be fixed for Guile and
other Schemes, but you'd still need to gut around half of it.
There haven't been any patches yet, but that doesn't mean I haven't been
spending time thinking about all this :)
--
Ian Price -- shift-reset.com
"Programming is like pinball. The reward for doing it well is
the opportunity to do it again" - from "The Wizardy Compiled"
prev parent reply other threads:[~2013-10-05 8:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-09 17:35 and-let* is not composable? Panicz Maciej Godek
2013-09-09 20:26 ` Stefan Israelsson Tampe
2013-09-09 21:34 ` Ian Price
2013-09-10 13:42 ` Stefan Israelsson Tampe
2013-09-10 13:51 ` Ian Price
2013-11-02 2:39 ` Ian Price
2013-11-02 19:01 ` Ian Price
2013-09-10 17:57 ` Ian Price
2013-09-11 12:25 ` Panicz Maciej Godek
2013-09-11 14:05 ` Ian Price
2013-09-13 18:40 ` Panicz Maciej Godek
2013-09-14 8:19 ` Stefan Israelsson Tampe
2013-10-04 22:27 ` Panicz Maciej Godek
2013-10-05 8:00 ` Ian Price [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=87fvsgcfkf.fsf@Kagami.home \
--to=ianprice90@googlemail.com \
--cc=godek.maciek@gmail.com \
--cc=guile-user@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).