From: Daniel Brockman <daniel@...>
Date: 2005-07-27T10:48:36+09:00
Subject: Re: What's so special about operators, built-in classes and modules?

One week and five days ago,

Joe Van Dyk <joevandyk@gmail.com> writes:

> I thought that the methods and constants in a module were
> just inserted into a class.

Daniel Brockman <daniel@brockman.se> writes:

> Yet another reason why modules and classes should
> be unified.

Austin Ziegler <halostatue@gmail.com> writes:

> I don't see it, personally.  I really don't see why they
> should be unified in the least.

Twelve hours ago,

Jim Freeze <jim@freeze.org> writes:

> For some reason I always thought that including a mod
> would shadow old methods.

Dear Austin,

While the superficial and cosmetic difference between these
two almost completely equivalent concepts continue to
mislead users, do you still not see “in the least” any
reason whatsoever to unify them?

Oh, and before someone comes shouting “but classes can be
instantiated and modules can't,” let me just post this:

   class Module
     def new(*a, &b)
       const_defined?(:Viagra) or
         const_set(:Viagra, Class.new.include(self))
       const_get(:Viagra).new(*a, &b)
     end
   end

-- 
Daniel Brockman <daniel@brockman.se>

    So really, we all have to ask ourselves:
    Am I waiting for RMS to do this?   --TTN.