unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Stefan Israelsson Tampe <stefan.itampe@gmail.com>
To: Andy Wingo <wingo@pobox.com>, guile-devel <guile-devel@gnu.org>
Subject: Re: syntax closures
Date: Tue, 22 Jan 2013 17:19:55 +0100	[thread overview]
Message-ID: <CAGua6m0qa75hkCmUWRu8vdXtx0j4E7XLq-ETp2pYzxGOj8budA@mail.gmail.com> (raw)
In-Reply-To: <87ip6pv0jm.fsf@pobox.com>

Hi


On Tue, Jan 22, 2013 at 1:56 PM, Andy Wingo <wingo@pobox.com> wrote:
>
> Hi,
>
> On Thu 17 Jan 2013 21:51, Stefan Israelsson Tampe <stefan.itampe@gmail.com> writes:
>
> > Hi all, I wanted to resurrect the idea of a syntactic closure. I did
> > some thinking and
>
> Meta: I seem to be receiving your mails with this really strange line
> wrapping.  It's been this way for a while, and it makes it difficult to
> read your mails.  Would you mind taking a look at your editor and
> setting the fill column to 72 characters?  Thanks :)

I'm using a web interface, poor me, I'll try to use a proper client
after this mail.

> > 2. The idea is to capture the syntactic environment in template1 ... and
> >  call the
> >     closure with the captured syntactic elements and insert the
> > resulting syntax into
> > .
>
> Into what?

Heh, I misstakenly pushed a send shortcut that mixed badly with emacs
keybindings. Anyway the captured syntaxes is then inserted in their positions.
There are a few caveats with the approach, see the code file in the repo for
a discussion of that.

> > (read-hash-extend #\_ syntax-closure-reader)
>
> Have you tried having your srfi-72 module export a binding for unsyntax?

I would like to use that of cause, but does it mix well with other
already written code?

> > The question for me is how to treat this code, as a library of it's
> > own supporting e.g. racket and guile and other schemes with the
> > syntax case system, or should we try to make this reader extension as
> > nice as possible and incorporate the code in guile. Is #_ ok? do you
> > have any other suggestion?
>
> I would prefer not to include it in the core; in my ignorance I do not
> see the need, especially if it can be implemented in a library.  Of
> course it may make sense to bundle a srfi-72 implementation with guile,
> but ideally we can do so without affecting the core.

I would like to be able to set this feature on per port bases just
like we do with
other reader features. Don't know to what a degree you need to do to
achieve this.
Is it something that a library can do? This relates to the previous
question. Anyway
I just thoght your thoughts and published a repo,

https://gitorious.org/syntax-closures

And I also suggeted to ijp to put it into guild-hall.

Regards
Stefan



  reply	other threads:[~2013-01-22 16:19 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 [this message]
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

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=CAGua6m0qa75hkCmUWRu8vdXtx0j4E7XLq-ETp2pYzxGOj8budA@mail.gmail.com \
    --to=stefan.itampe@gmail.com \
    --cc=guile-devel@gnu.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).