On Jan 28, 2005, at 8:42 AM, PA wrote:

>
> On Jan 28, 2005, at 15:29, James Edward Gray II wrote:
>
>> * If a Ruby core method isn't behaving quite like you need it to, 
>> just edit it to fit your task.
>
> This sounds very much like the ultimate "nuclear" option in 
> Objective-C... after indiscriminately applying +poseAsClass: left and 
> right add some random "method swizzlings" for good measure...
>
> http://www.cocoadev.com/index.pl?MethodSwizzling
>
> Not recommended. Even when you think you know what you are doing in 
> the first place.

Hmm, I would say it's a fairly common Ruby practice.  Adding method to 
the classes is even more so.

Doesn't Rubygems replace require(), just to give an example?

The require() hack earlier in this thread looked quite handy to me.

James Edward Gray II