| Scoping Hell |
[Mar. 15th, 2005|08:18 pm] |
I was just reading a translation of Matz's blog, courtesy of _why, regarding his ideas for scoping changes in Ruby 2.0
Wasn't I just bragging about how Ruby wouldn't suffer from SSE in 2.0? Well, I may have to eat those words if Matz continues on what I consider a path towards scoping disaster. The syntax is ugly, it's not intuitive to either newbies or advanced programmers, and it has bizarre restrictions: local variables must be unique? local variables must be declared in the block parameter?! WHAT THE ...?!?!
One can only imagine how handling this within a C extension would look, or the cacophony of questions that will appear on the mailing list as a result of this grotesque syntax. I'm sure as hell not going to answer them. Are you? This is the sort of change that would force me to stick with 1.8.x while I start shopping around for a new language. I kid you not.
I agree with Phil - the current scoping quirks are minor, and I'd prefer to leave things as they are compared to this proposal. |
|
|
![[info]](http://l-stat.livejournal.com/img/userinfo.gif){kind=small}
djberg96's journal