From: Mathieu Bouchard <matju@...>
Date: 2003-08-25T03:29:57+09:00
Subject: Re: differences between Module and Class ?


On Sun, 24 Aug 2003, Chad Fowler wrote:

> Matju, is there any reason to do this other than idealism?

Chad, wasn't the module/class distinction a similarly "idealistic" move in
the first place? I mean it seems to be on the same level of thought than
what I propose. Then why is the so-called "idealism" inappropriate when it
comes from me?

> We've beaten this thing to death in terms of why *not* to do it,

I can't share this opinion. A lot may have been said, but I suspect that
not so much has been understood, and certainly that few people have
participated in it. You seem to have a different standard on what "beating
to death" may mean.

Additionally this is not a complete proposal. There is an uncertain
element that may very well make the difference between a proposal that I
would myself approve and one that I wouldn't, but no-one has answered me
on that.

Another thing I want to complete before submitting anything seriously, is
to understand the current situation... so even if my proposal gets dumped,
and even if I dump my proposal myself, I still want to understand the
current situation correctly, and this has not happened yet.

> But, why *should* this change?

I've presented this already. [ruby-core:1448]. The actual advantages may
get more precise as the details get more precise.

> What is the real practical benefit?

You mean that the reasons I've presented yet are not practical enough for
you. I'm sorry I can't help you for now, especially as I don't completely
understand the current situation yet, even after "beating this thing to
death" as you call it.

> What could we do that we can't do now?

Not all changes worth doing fall into that category. Else chances are that
I would have sticked with another language and never would have bothered
with Ruby.

________________________________________________________________
Mathieu Bouchard                       http://artengine.ca/matju