4 ms·
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 sensit
by jlangenauer 16y ago
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 http://github.com/jasonl/eden - which made me deal with the dusty, hidden corners of the Ruby grammar.)
- scott_s 16y agoHow does this make the language harder to parse?
- lelele 16y agoOnly ruby will be able to parse Ruby ;-) Ruby is just showing its Perl roots.
- wazoox 16y agoGiven that the hashrocket came from Perl to Ruby primarily, and that it changed to look more like Python, I'd say you're wrong :)
- lelele 16y agoWell, 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 http://www.ruby-forum.com/topic/152544