unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Marijn <hkBst@gentoo.org>
To: dwheeler@dwheeler.com
Cc: almkglor@gmail.com, guile-devel@gnu.org
Subject: Re: Adding to guile curly-infix (SRFI 105), neoteric- & sweet-expressions
Date: Mon, 27 Aug 2012 13:20:30 +0200	[thread overview]
Message-ID: <503B57FE.6020606@gentoo.org> (raw)
In-Reply-To: <E1T5gE7-0006EY-Up@fenris.runbox.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi David,

On 26-08-12 19:02, David A. Wheeler wrote:
> 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

I watched your presentation and you have a pleasant voice.

I don't have anything to remark about (your) syntax for infix notation.

About the proposed function call syntax (really dislike the `neoteric'
(new poetic?) name), I do want to make some remarks. It seems that
your transformation rules depend on a non-parenthesized context (or
some other unspecified constraint), otherwise your rule e{...} |-> (e
{...}) can be applied to itself and leads to e{...} |-> ((((e
{...})))) among other things, such as:

cons{1}{2} |-> (cons{1}){2} |-> (cons 1){2} |-> ((cons 1){2}) |->
((cons 1) 2)

but also

cons{1}{2} |-> cons{1} 2 |-> cons 1 2 |-> (cons 1 2).

Using `f(1 2) |-> (f 1 2)' you can push open parens left meaning (a (b
c)) is equal to ((a b c)).

Can you shed some light on these issues?

Marijn

> 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/

PS "{x + y) actually generates {+ x y)"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlA7V/4ACgkQp/VmCx0OL2wVzQCgwCUu6DMR1owjKRoqxe4RZxl9
M3sAmgKB0Ww/99MBJ1RIVultm6R+SbcI
=lUEC
-----END PGP SIGNATURE-----



  parent reply	other threads:[~2012-08-27 11:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-26 17:02 Adding to guile curly-infix (SRFI 105), neoteric- & sweet-expressions David A. Wheeler
2012-08-27  2:11 ` 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 [this message]
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=503B57FE.6020606@gentoo.org \
    --to=hkbst@gentoo.org \
    --cc=almkglor@gmail.com \
    --cc=dwheeler@dwheeler.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).