From: stefan.itampe@gmail.com
To: guile-devel@gnu.org
Subject: Programming racket like in guile
Date: Thu, 21 Feb 2013 21:59:17 +0100 [thread overview]
Message-ID: <1787022.v0icS3ncxM@warperdoze> (raw)
Dear guilers!
I have spend quite a lot of work porting racket code to guile
e.g. syntax-parse and the code for contracts, as a spinoff I have
done several other parts as well e.g.
* contracts (guile-contract)
* syntax parse (guile-syntax-parse)
* some support for racket lambda argumnets
lambda list (guile-syntax-parse)
* some support for racket structs (guile-contract)
* racket matcher (guile-syntax-parse)
* racket for loops (racket-loops-for-guile)
* may things I have forgotten about
Is there something in here that you would like to improve on or are
there
components in the racket codebase that you would like to have in guile
so please let me know!
I also suggest that for people writing compatability code that we have
a standard namespace for this. Let me suggest
(compat name-of-scheme/lisp component ...)
e.g.
(compat racket match)
(compat racket for)
(compat racket struct)
The idea is that we push code here that is useful for porting
the components that we are actually interesting to have in guile
like syntax-parse.
for the code that we deem so useful that we would like to push it to a
more
descriptive location we will of cause do that as well e.g. (syntax
parse)
WDYT
Cheers!
Stefan
next reply other threads:[~2013-02-21 20:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-21 20:59 stefan.itampe [this message]
2013-02-22 15:56 ` Programming racket like in guile 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
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=1787022.v0icS3ncxM@warperdoze \
--to=stefan.itampe@gmail.com \
--cc=guile-devel@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).