From: transfire@...
Date: 2006-06-09T23:15:21+09:00
Subject: Re: Why the lack of mixing-in support for Class methods?


Yukihiro Matsumoto wrote:

> I like this more than others, but I worry about that this is less
> descriptive than other at the same time.  For example, how one can
> know whether "include" does not injects module methods, where "<<"
> does.

Unfortuantly, as it is, we cannot know. I have seen some bad practices
in the overriding of #include which do not ever inject the module. It's
weird becuase Ruby reports the module as an ancestor though the module
is totaly devoid of any content, i.e. The #include call was just used
as a "trick" to do something else (usually using class_eval to add
methods directly to the base class/module).

Short of turning include and extend into keywords, I'm not sure there's
any way to ensure proper behavior. And if that were done, it would
likely create other limitations that may have been useful to more
experienced Rubyists.

T.