From: MikkelFJ <mikkelj-anti-spam@...1.dknet.dk>
Date: 2001-08-12T02:43:41+09:00
Subject: [ruby-talk:19541] Re: order and freedom in Ruby (was: Re:  Re: the way class variables work)


"ts" <decoux@moulon.inra.fr> wrote in message
news:200108111511.f7BFBZX08156@moulon.inra.fr...
> >>>>> "M" == MikkelFJ  <mikkelj-anti-spam@post1.dknet.dk> writes:
>
> M> I have never tried, I just assumed that once you had created your
class,
> M> changes to parent would not be transparent.
>
>  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.

Ruby is easy to learn, but difficult to master.
And like fire it is a very useful friend, and a very dangerous enemy.


Mikkel