Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I have to say I cried a little bit when I read this - it seems that Matz et al are trying to make the language unparseable.

(Of course, perhaps I'm more sensitive than most, having actually written an Ruby lexer - http://github.com/jasonl/eden - which made me deal with the dusty, hidden corners of the Ruby grammar.)



How does this make the language harder to parse?


Only ruby will be able to parse Ruby ;-)

Ruby is just showing its Perl roots.


Given that the hashrocket came from Perl to Ruby primarily, and that it changed to look more like Python, I'd say you're wrong :)


Well, the pun was not about the => operator, but about Ruby becoming "less parseable". As they say: "Only perl can parse Perl" ;-)

So => is the "hashrocket" operator? I can't find any reference to this name besides this: http://www.ruby-forum.com/topic/152544


I suppose. It goes well with the spaceship operator <=>.


Now we need to find a meaning for |=| so it can be the Tie Fighter operator.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: