[racket-dev] P4P: A Syntax Proposal

I've always thought the problem was the parens.  But I just realized
that besides prefix and excessive parens there is one more problem, and
that is using function application to encode structure.

E.g. (if c t f) is really structure.  Shriram's syntax handles this by
adding in extra markers for readability.

E.g. 
  (map (lambda (x) ...) 
       lst)
is more readable in the Ruby form:
  map(lst) {|x| ... }
or even in Javascript with Prototype:
  lst.each(function(x) {
    ...
  });

-Everett

On Wed, 2010-07-28 at 16:36 -0400, Shriram Krishnamurthi wrote:
> People already struggle with nesting.  Excessive parens make
> composition look much harder than it is.  Ergo, my desire to remove
> all unnecessary parentheses.
> 
> While agreeing on goals (integration w/ reader, etc.), I'm ultimately
> less interested in H-expressions than in the surface language.  That
> is, I want a good surface syntax *with* a good back-end.
> 
> Shriram
> _________________________________________________
>   For list-related administrative tasks:
>   http://lists.racket-lang.org/listinfo/dev