From: Joel VanderWerf <vjoel@...>
Date: 2006-06-15T04:18:15+09:00
Subject: Re: Why the lack of mixing-in support for Class methods?

transfire@gmail.com wrote:
> Problem is that 'extend @class_extension' doesn't work unless it occurs
> _after_ the module_eval(&blk). Which means later changes to the
> extensions module will have no effect on modules that have already
> included it. Not good. So unless I've misanalyzed this, I think keeping
> a running list of extension modules, more like my previous
> implementation post, is going to be neccessary.

Why should the order of calling extend and adding methods matter? It
doesn't seem to in this example, but this is much simpler than
class_extension:

module M
  def foo; p "FOO"; end
end

class C
  extend M
end

module M
  def bar; p "BAR"; end
end

C.foo
C.bar

__END__

"FOO"
"BAR"

-- 
      vjoel : Joel VanderWerf : path berkeley edu : 510 665 3407