From: transfire@...
Date: 2006-06-12T13:37:25+09:00
Subject: Re: Why the lack of mixing-in support for Class methods?


Yukihiro Matsumoto wrote:

> It may make sense from some aspect, but not from others.  Language
> design is the very complicated task. ;-)

I concur with that. It is certainly not a simple thing, and I can only
admire the work you have done in the field. That's for sure.

> In this case, it introduces full multiple inheritance, which I avoided for years.

Does it really introduce multiple inheritance? It's still a linear
heirarchy. I always thought of MI as a means to route calls to
ancestors in arbitrarily defined ways, more like a tree graph. So I'm
not sure how the modularization of a module's "class methods" is
multiple inheritance other than the fact that a class is gaining new
behaviors from the module, making it something more than it was before.
But we can do that already with #extend.

I guess what I don't understand is this: If I can manully separate the
"class-level" into it's own module and resuse that, why can't I just
reusue the class-level to begin with?

T.