Thank you, Matz... see below.

> Well, Mix-in is not a "interface polymorphism", it's a variation of
> "inheritance polymorphism".

Well, OK... the receiver certainly gains new functionality from the
mix-in.

Can we truly say, then, that Ruby does not support multiple inheritance?
Why do we have modules instead of ordinary MI? (I did read your article
in InformIT.)

Pardon my confusion.

> An example of "interface polymorphism" is Enumerable module, which
> requires a mixing class to have `each' method and that's all.  No
> inheritance relation is needed.

OK, I see that.

Thanks,
Hal

--
Hal Fulton


Sent via Deja.com http://www.deja.com/
Before you buy.