From: Stefan Israelsson Tampe <stefan.itampe@gmail.com>
To: guile-devel@gnu.org
Cc: "Ludovic Courtès" <ludo@gnu.org>
Subject: Re: Programming racket like in guile
Date: Sun, 24 Feb 2013 22:47:46 +0100 [thread overview]
Message-ID: <16023209.idbI5B2ATb@warperdoze> (raw)
In-Reply-To: <87txp12zfr.fsf@gnu.org>
On Sunday, February 24, 2013 10:07:36 PM Ludovic Courtès wrote:
> What would have been nice IMO is to import, say, ‘syntax-parse’ and
> contracts, without having to pull in a whole compatibility layer.
>
> Ludo’.
I would say that I tried more to make syntax-parse
independent. contracts on the other hand depends on syntax-parse for
loops racket structs etc. That said syntax parse is quite a hefty
sized library.
/Stefan
next prev parent reply other threads:[~2013-02-24 21:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-21 20:59 Programming racket like in guile stefan.itampe
2013-02-22 15:56 ` Ludovic Courtès
2013-02-22 19:04 ` stefan.itampe
2013-02-24 21:07 ` Ludovic Courtès
2013-02-24 21:47 ` Stefan Israelsson Tampe [this message]
2013-02-23 0:54 ` Daniel Hartwig
2013-02-23 2:32 ` Ian Price
2013-02-23 15:39 ` Noah Lavine
2013-02-23 16:28 ` Stefan Israelsson Tampe
2013-02-23 12:44 ` Stefan Israelsson Tampe
2013-02-23 15:36 ` Noah Lavine
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=16023209.idbI5B2ATb@warperdoze \
--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).