[ruby-talk:03833] Re: Order of overwriting

> When you include a module in a class, you've affectively making that
> module a parent of the class[1]. As such, it gets inserted between the
> class and the class' original parent:
> 
>       Bar  -->  Zak
> 
>    "include Foo"
> 
>       Bar  -->  Foo --> Zak
> 
>    "include Foo_update"
> 
>       Bar  -->  Foo_update --> Foo --> Zak

Really clear! Thank you.

Now I just have to give some time for my mental model to adjust. It just got
used to the idea the Ruby reads source and processes it as it goes, like:

puts "foo"         # first seen
class Foo          # second thing to see, transfers the interpreter to 
                   # here-comes-a-class-definiton state
  def foo          # changes to a here-comes-a-method-definition state
    puts "bar"     # adds some code to Foo#foo
  end
end

Now I think it will change into:

class Foo          # change to a here-comes-a-class-definition(-remember-
                   # to-scan-through-the-definition-first)
  def foo
  end
  include "Bar"    # whee, here we have it, now we can start to read method
                   # definitions
end

So kind of two pass thing. But I think I'm that flexible, I can learn one
more twist :).

	- Aleksi