From: Stefan Israelsson Tampe <stefan.itampe@gmail.com>
To: Mark H Weaver <mhw@netris.org>
Cc: Andy Wingo <wingo@pobox.com>, guile-devel <guile-devel@gnu.org>
Subject: Re: syntax closures
Date: Fri, 15 Feb 2013 11:08:08 +0100 [thread overview]
Message-ID: <CAGua6m024fsbnZhrh6hTSdmY_B5LAOOLjtnO1vxvCnvUN=vpSg@mail.gmail.com> (raw)
In-Reply-To: <87sj4y1ab1.fsf@tines.lan>
BTW.
Of cause if you read the doc's for srfi-72 you will see a whole
different machinery that brings many features, they explicitly states
6 facts in the abstract for which I adress one in the code.
On the other hand when they try to sell it it they just uses examples
for the case for witch I try to implement a solution for. So in this
light I would say that I practically cover 90% of srfi-72 intention.
But from a theoretical standpoint I would just say 10%.
/Stefan
On Fri, Feb 15, 2013 at 5:16 AM, Mark H Weaver <mhw@netris.org> wrote:
> Stefan Israelsson Tampe <stefan.itampe@gmail.com> writes:
>> Let's call it guile-srfi-72, In the end it is a srfi-72 simulator [...]
>
> I'm pretty sure this is also false. One of the main points of SRFI-72
> is the improved hygiene algorithm, which is quite different than psyntax
> in its details. Unless I'm mistaken, you have picked out only one small
> aspect of SRFI-72 that happens to be relevant to what you're doing.
>
> Therefore, I don't think it should be called SRFI-72 either.
>
> Mark
prev parent reply other threads:[~2013-02-15 10:08 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
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 [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='CAGua6m024fsbnZhrh6hTSdmY_B5LAOOLjtnO1vxvCnvUN=vpSg@mail.gmail.com' \
--to=stefan.itampe@gmail.com \
--cc=guile-devel@gnu.org \
--cc=mhw@netris.org \
--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).