From: dejaspam@... (Bill Atkins)
Date: 2004-05-26T06:43:45+09:00
Subject: How are mixins better than multiple inheritance?

Can anyone explain how Ruby's mixin system is better than regular
multiple inheritance?  What's the difference between:

----

module Parent1
    def amb_func
        puts "in parent1"
    end
end

module Parent2
    def amb_func
        puts "in parent2"
    end
end

class Child
    include Parent1, Parent2
end

Child.new.amb_func

----

and

----

class Parent1
    def amb_func
        puts "in parent1"
    end
end

class Parent2
    def amb_func
        puts "in parent2"
    end
end

class Child < Parent1, Parent2
end

Child.new.amb_func

---

Aside from the fact that the second example obviously isn't valid
Ruby, how is the first scenario an improvement over the second?  The
first outputs "in parent2" and I assume the second would as well.  Can
somebody please explain this?

Bill