From: "David A. Wheeler" <dwheeler@dwheeler.com>
To: guile-devel@gnu.org
Cc: almkglor@gmail.com
Subject: Adding to guile curly-infix (SRFI 105), neoteric- & sweet-expressions
Date: Sun, 26 Aug 2012 13:02:19 -0400 (EDT) [thread overview]
Message-ID: <E1T5gE7-0006EY-Up@fenris.runbox.com> (raw)
All:
I'd really like feedback on proposed new SRFIs, and I'd like to help get these SRFIs implemented in guile.
Background: The "readable" group has developed and refined 3 new reader abbreviations for Scheme: curly-infix-, neoteric-, and sweet-expressions. Each builds on the previous one; details are here:
http://readable.sourceforge.net
We plan to submit all three abbreviations as three separate SRFIs. The first one, curly-infix-expressions, is new draft SRFI 105, and we'd ESPECIALLY like comments on that:
http://srfi.schemers.org/srfi-105/
The whole point of a SRFI is to get it *implemented*, so if you have a comment (such as a *problem* with them or getting any of them implemented in guile), please let us know!! The best way to comment is the mailing lists (for the SRFIs or via readable.sourceforge.net), so that everyone can discuss and address them.
Also, I'd be happy to help get these implemented as part of guile. We have a current implementation that builds on *top* of guile (by completely re-implementing the reader), but it'd far better to have these built-in.
Thanks for your time!
--- David A. Wheeler
next reply other threads:[~2012-08-26 17:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-26 17:02 David A. Wheeler [this message]
2012-08-27 2:11 ` Adding to guile curly-infix (SRFI 105), neoteric- & sweet-expressions nalaginrut
2012-08-27 4:16 ` David A. Wheeler
2012-08-27 4:30 ` Alan Manuel Gloria
2012-08-28 2:57 ` Noah Lavine
2012-08-28 6:56 ` Alan Manuel Gloria
2012-08-27 11:20 ` Marijn
2012-09-01 3:16 ` David A. Wheeler
2012-08-28 20:43 ` Ludovic Courtès
2012-08-29 1:49 ` David A. Wheeler
2012-08-29 7:54 ` Alan Manuel Gloria
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=E1T5gE7-0006EY-Up@fenris.runbox.com \
--to=dwheeler@dwheeler.com \
--cc=almkglor@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).