From: "Hal E. Fulton" <hal9000@...>
Date: 2003-04-25T01:53:02+09:00
Subject: Re: Subject: Re: [ANN] Ruby.shop

----- Original Message -----
From: "Chris Pine" <nemo@hellotree.com>
To: "ruby-talk ML" <ruby-talk@ruby-lang.org>
Sent: Thursday, April 24, 2003 11:39 AM
Subject: Re: Subject: Re: [ANN] Ruby.shop


> ----- Original Message -----
> From: "Hal E. Fulton" <hal9000@hypermetrics.com>
>
> But as for arrow color: Is it not worthwhile distinguishing
> between "X inherits from Y" and "X mixes in Y"?
> ----------------------------
>
> It doesn't seem important to me either way, so I would leave them all the
> same color by default.  The two concepts are so similar... as I understand
> it, when X mixes in Y, X is just inheriting from Y's proxy class.
>
> I think of these arrows as saying, "These are the methods you can call
this
> kind of object."  In that light, it makes no difference if it is getting
> them from a class or from a module.

True. I'm still inclined to distinguish on the
basis that when you inherit, you (can) get instance
data, whereas when you mix in, you typically don't.

As I think about this, though, even that may be a
false distinction. What do you think?

Hal