On Wednesday 17 December 2003 09:26 am, Yukihiro Matsumoto wrote:
> Hi,
>
> In message "Mixin Module, Possible Bug?"
>
>     on 03/12/17, "T. Onoma" <transami / runbox.com> writes:
> |This produces:
> |
> |  1. WC == WC
> |  2. WAC == WC
> |  3. WAC == WAC
> |
> |Number #2 should produce WAC, given the dynamic behavior of Ruby, and just
> | as the PickAxe describes, there is but one Module W. So how is it that c1
> | does NOT RESPOND to the inclusion of A, although the new c2 does?
>
> This is part of weakness of Ruby's module system.
>
> Including module into another module does not affect already created
> instance/class/module.

Thanks matz,

How is that possible? Isn't the module just linked to the other module via a 
proxy? Or is something actually being copied?

-- 
T.