Re: paren-free call expressions

2011-05-26 Thread Lasse Reichstein
On Thu, 26 May 2011 07:15:31 +0200, David Griffiths dxgriffi...@gmail.com wrote: Many, many languages (including Perl, Ruby, VB, Scala, Smalltalk, Logo, and of course all the ML-like languages, including Haskell and F#) do without parentheses for calls in some circumstances at least. Do you

Re: paren-free call expressions

2011-05-26 Thread Claus Reinke
ECMAScript doesn't curry its function declarations. A function does take all its arguments at once (and not as a tuple value), and since we can even supply too few or too many arguments when calling a function, trying to mimic SML will only bring pain. I thought so, too, for a long time. But

Re: paren-free call expressions

2011-05-25 Thread David Griffiths
Sure, My rationale is that people reading code are not the same as parsers :) If a space is sometimes just a space, and sometimes it is effectively an implied (, then the comprehension difficulty is increased. If you could measure it with an eye-tracking system, I suspect that savings like

Re: paren-free call expressions

2011-05-20 Thread Jason Orendorff
On Thu, May 19, 2011 at 2:45 AM, David Griffiths dxgriffi...@gmail.com wrote: - they overload the space character, making it mean something different in only a small fraction of cases. [...] The first point is major, in my opinion. If the goal is to have an argument list opener that

Re: paren-free call expressions

2011-05-19 Thread David Griffiths
Hi all, I'm new to this list but I was writing some notes about paren-free calls this morning and thought they might be relevant. The trouble with paren-free calls, as implemented in CoffeeScript and others: - they overload the space character, making it mean something different in only a

paren-free call expressions

2011-05-18 Thread Dmitry A. Soshnikov
Hi, Parens-free call expression allow to provide some actions /decoratively/. From this, the consequence of easy and elegant DSLs (domain specific languages). For example: class Account { attributes customer, cart } Thus, call to `attribute` function looks like not the imperative call,

Re: paren-free call expressions

2011-05-18 Thread Brendan Eich
I'm working on a block-as-better-function proposal, essentially an alternative to arrow-function-syntax even though unlike the latter, the former has new semantics. One of the insights from Allen and Mark, which is kind of obvious to Rubyists, is that blocks as lightweight functions usable for

Re: paren-free call expressions

2011-05-18 Thread Dmitry A. Soshnikov
On 18.05.2011 20:16, Brendan Eich wrote: I'm working on a block-as-better-function proposal, essentially an alternative to arrow-function-syntax even though unlike the latter, the former has new semantics. One of the insights from Allen and Mark, which is kind of obvious to Rubyists, is that