From: Florian Gilcher <flo@...>
Date: 2008-03-01T08:41:44+09:00
Subject: Re: Proposed Solutions - Was [ Re: Monkeypatching is Destroying Ruby ]


On Feb 29, 2008, at 11:29 PM, James Britt wrote:

> hemant wrote:
>
>> James, Sometime ago Rick Olson wrote this:
>> http://weblog.techno-weenie.net/2007/12/19/adventures-in-rails-debugging
>> Does ring a bell, doesn't it?
>
> No.  Why should it?
>
> I try to avoid Rails.
>
> Too annoying.
>

Well, Rails internals are truly gruesome sometimes. I just had a long  
session trying to change some behaviour in the routing system. There  
are multiple real  wtfs in it... well, back to topic.

>
>
>> ...
>> My point is, I love open classes, but it shouldn't hurt to have  
>> little
>> bit of safety precaution built into the language, does it?
>
>
> Ah HA!  I *knew* it!
>
> It's the static typing permathread in disguise.
>

Hehe, it may be... i don't think we that another language construct  
helps. As some have illustrated, all those problems can be solved with  
discipline on both sides (authors and users). If i wanted a language  
construct for everything, i'll head back to Java || C++.

The only solution that would be an addition to the language would be  
real selector namespaces.

Greetings
Skade