From: Ian White <ian.w.white@...>
Date: 2006-12-22T00:35:07+09:00
Subject: Re: extend weirdness?

The previous post is using a rails-style idiom, which is unnecessarily
complex for the problem at hand.
Here's a simpler example to the same effect:

    module Foo
      def self.included(base)
        class<<base
          def meth
            "Foo"
          end
        end
      end
    end

    module Bar
      def meth
        "Bar"
      end
    end

    class A
      include Foo
      extend Bar
    end

    puts A.meth

Which produces "Foo"

There's a workaround (remove the method by hand):

    module Bar
      def self.extended(base)
        class<<base
          remove_method :meth
        end
      end
    end

But this workaround does what I'd expect Ruby to do (overwrite any
existing methods when extending)

I'm confused - is this expected behaviour?

Cheers,
Ian

ps.

$ ruby --version
ruby 1.8.5 (2006-08-25) [powerpc-darwin8.7.0]