On Fri, 1 Mar 2013, Yoshiki Ohshima wrote:

> I believe I have seen Dan Ingalls posted about the syntax here
> before...  The essence of the message was that a block is still like a
> method, and they kind of have keyword message pattern, except that the
> keyword part is null (0-length) string.  In this regard, allowing
> spaces after a colon follows the principle.

That's pretty cool and exactly what I always thought about it, but I still 
couldn't find a good reason for the | at the end of the block signature. 
Without it blocks could be parsed just like methods, (probably) making the 
parser simpler:

array collect: [ :each
 	each * each ]


Levente

>
> I thought that why we don't allow keywords longer than 0, actually.
> One could say:
>
> [keyword1: arg1 keyword2: arg2 | ...]
>
> to annotate each parameter of a block.
>
> -- 
> -- Yoshiki
>
>