From: Alex Shinn <alexshinn@gmail.com>
To: Stefan Israelsson Tampe <stefan.itampe@gmail.com>
Cc: Andy Wingo <wingo@pobox.com>, guile-devel <guile-devel@gnu.org>
Subject: Re: syntax closures
Date: Thu, 24 Jan 2013 17:45:23 +0900 [thread overview]
Message-ID: <CAMMPzYO_4YthaTxnfVbH8pV6u31P2QEwZaT1YyLsR7A+5tJpcg@mail.gmail.com> (raw)
In-Reply-To: <CAGua6m3aHyzw2c1x9xtVsa0JRBdxy9HoC=M+XzmQMEde3eJeLA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 596 bytes --]
On Thu, Jan 24, 2013 at 4:11 PM, Stefan Israelsson Tampe <
stefan.itampe@gmail.com> wrote:
>
> 2. I was actually hesistant to call this srfi-72 because of trying to
> do what it want
> more than what it say's. A main trick to simulate the effect was to
> introduce
> a closure in the syntax at one point and therefore a choose the name
> syntax-closure not knowing that there is an already a notion of
> that in the wild
>
Oh - I thought you were referring to the existing syntactic-closures.
I guess it's a plausible enough name to reuse coincidentally...
Carry on then :)
--
Alex
[-- Attachment #2: Type: text/html, Size: 1105 bytes --]
next prev parent reply other threads:[~2013-01-24 8:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-17 20:51 syntax closures Stefan Israelsson Tampe
2013-01-22 12:56 ` Andy Wingo
2013-01-22 16:19 ` Stefan Israelsson Tampe
2013-01-22 16:38 ` Andy Wingo
2013-01-22 19:06 ` Stefan Israelsson Tampe
2013-01-22 20:37 ` Stefan Israelsson Tampe
2013-01-23 23:24 ` Stefan Israelsson Tampe
2013-01-24 2:08 ` Alex Shinn
2013-01-24 7:11 ` Stefan Israelsson Tampe
2013-01-24 8:45 ` Alex Shinn [this message]
2013-02-14 9:42 ` Mikael Djurfeldt
2013-02-14 11:13 ` Stefan Israelsson Tampe
2013-02-15 4:16 ` Mark H Weaver
2013-02-15 9:34 ` Stefan Israelsson Tampe
2013-02-15 10:08 ` 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=CAMMPzYO_4YthaTxnfVbH8pV6u31P2QEwZaT1YyLsR7A+5tJpcg@mail.gmail.com \
--to=alexshinn@gmail.com \
--cc=guile-devel@gnu.org \
--cc=stefan.itampe@gmail.com \
--cc=wingo@pobox.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).