[#4595] New block syntax — Daniel Amelang <daniel.amelang@...>

I'm really sorry if this isn't the place to talk about this. I've

25 messages 2005/03/21
[#4606] Re: New block syntax — "David A. Black" <dblack@...> 2005/03/21

Hi --

[#4629] Re: New block syntax — "Sean E. Russell" <ser@...> 2005/03/30

On Monday 21 March 2005 16:17, David A. Black wrote:

[#4648] about REXML::Encoding — speakillof <speakillof@...>

Hi.

15 messages 2005/03/31
[#4659] Re: about REXML::Encoding — "Sean E. Russell" <ser@...> 2005/04/04

On Thursday 31 March 2005 09:44, speakillof wrote:

Re: New block syntax

From: "Berger, Daniel" <Daniel.Berger@...>
Date: 2005-03-21 20:49:11 UTC
List: ruby-core #4604
> -----Original Message-----
> From: Mathieu Bouchard [mailto:matju@sympatico.ca] 
> Sent: Monday, March 21, 2005 1:40 PM
> To: ruby-core@ruby-lang.org
> Subject: Re: New block syntax
> 
> 
> 
> On Tue, 22 Mar 2005, Berger, Daniel wrote:
> 
> > I extremely DISLIKE the new proposed syntax for 
> proc/blocks.  I would 
> > rather we kept lambda/proc keyword mandatory, rather than 
> end up with 
> > goofball syntax like the above, just so we can make anonymous procs 
> > more Perly.
> 
> Could you please tell us what makes the new syntax more 
> Perly, and the old syntax not Perly? Especially, please 
> comment on the following
> examples:

I was thinking of sub references in Perl/Tk actually.  But, the "Perly"
mention is hardly the point of my jab.  My point is that the new syntax
looks bad and will cause no end of confusion with Hash syntax now and
into the future, IMHO.  I just don't understand the push to alter
existing syntax all so we can avoid typing the word "proc".

There's a fine line between terse and obfuscated, and I fear we're
slouching towards the latter.

Regards,

Dan



In This Thread

Prev Next