Hi --

On Wed, 22 Mar 2006, Wilson Bilkovich wrote:

> I wonder if there's a way to make several groups of people happy by
> allowing this:
> module Z
>  def method; end
> end
>
> class A < Z
> end
>
> ..which would let modules act as abstract classes if necessary.

There's definitely a school of thought that modules and classes should
be merged, though I am not of it and Matz isn't either :-)


David


> On 3/21/06, Trans <transfire / gmail.com> wrote:
>>> I don't think it's a good idea, because I see no reason to favor the
>>> hypothesis that a module's singleton methods are appropriate
>>> for a class
>>
>> What "hypothesis"? It's being used in *practice*.
>>
>> According to your argument we should not have class method inheritance
>> either.
>>
>> T.
>>
>>
>>
>
>

-- 
David A. Black (dblack / wobblini.net)
Ruby Power and Light, LLC (http://www.rubypowerandlight.com)

"Ruby for Rails" chapters now available
from Manning Early Access Program! http://www.manning.com/books/black