Re: Why the lack of mixing-in support for Class methods?

< :the previous in number ^ :the list in numerical order > :the next in number P :the previous artilce (have the same parent) N :the next (in thread) |<:the top of this thread >|:the next thread ^ :the parent (reply-to) _:the child (an article replying to this) >:the elder article having the same parent <:the youger article having the same parent ---:split window and show thread lists | :split window (vertically) and show thread lists ~ :close the thread frame .:the index ..:the index of indices

Daniel Schierbeck wrote: > Logan Capaldo wrote: > > Then you have multiple inheritance. > > Yes. Not really. Mulitple Inheritance provides orthogonal heirarchies. Ruby's is strictly linear. If what you say were true then Ruby would already be MI since modules can be used to add behavior to both class and instance levels, and readily associated together as well, as Ara's example clearly demonstrates. To think this consititutes MI and thus making specialized restrictions of code separation to repress it, only serves to complixify the situation, not the other way around. It's like trying to prevent someone from getting to their destinatin by not allowing them to turn right --they'll still get there, they'll just turn left three times. T.