From: Gavin Kistner <gavin@...>
Date: 2004-10-23T08:41:19+09:00
Subject: Re: #extend_object only for #extend and not #include

On Oct 22, 2004, at 8:09 AM, Robert Klemme wrote:
> "Gavin Kistner" <gavin@refinery.com> schrieb im Newsbeitrag
> news:8529C86C-2430-11D9-A186-000A959CF5AC@refinery.com...
>> Just thought I'd point out my surprise that the Module#extend_object
>> callback only fires when #extend is explicitly called, and not when 
>> the
>> module extends the class via #include:
> Well, that's quite logical, isn't it?  I mean, include and extend are 
> two
> different cups of tea.

Are they? Other than different receivers (and thus the ability for 
#extend to operate on instances) are they functionally different and 
I'm a moron for not realizing it?


>   def self.included( o )
>     p "#{o} just included #{self}"
>   end

Apparently I didn't know about this. That'll do...thanks! :)