From: Gregory Brown <gregory.t.brown@...>
Date: 2007-01-13T05:24:48+09:00
Subject: Re: inheritance concept in ruby

On 1/12/07, Helder Ribeiro <helder@gmail.com> wrote:

> That is, the exact same thing happens when you have a class include two
> modules and both implement the 'hello' method. There is no self-evident
> way of choosing, so you have to come up with an arbitrary choice like
> that of order of call to 'include'.

To me, it's the most intuitive choice as it reflects intrepretation order

class Child < Parent #imbue with ancestry

  include Foo # imbue with foo's definitions
  include Bar # imbue with bar's definitions

  def something  # imbue with actual definition

  end

 end

All that is happening is Ruby's applying the changes as it sees them.

So the path there is super clear

Child -> Bar -> Foo -> Parent.

Maybe this is surprising to those working in non-interpreted languages
though.  I'm not sure.