From: Mathieu Bouchard <matju@...>
Date: 2001-08-12T05:15:35+09:00
Subject: [ruby-talk:19546] Re: order and freedom in Ruby (was: Re:  Re: the way class variables work)


On Sun, 12 Aug 2001, MikkelFJ wrote:
>> There is at least one case where it's not totally transparent. This is
>> not really for parent but when you use a module, for example :
>
> I can understand it by thinking of a parent class as a parent pointer, and
> mixins as bulk copy operations.

mixins work with 'pointers' as well. I think the problem Guy is showing is
that Classes cache method lookup, but Modules don't implement Observable,
so Classes can't subscribe to them, so Classes can't know when Modules
change, and thus can't invalidate their caches.

Or something like that. (but Classes don't implement Observable either,
and Classes are Modules anyway, ...)

I'd call this a bug, but Guy knows more about it than I do.

matju