Class <=> module

ruby-talk
1

Hello all,

Recently I got the error described at
Warning: toplevel constant XYZ referenced Admin:XYZ - RSpec - Ruby-Forum,
which shows that classes can't be used to scope another classes or modules.

Then I started thinking: why two concepts, class and module, instead of
only one?

Classes heritage, a feature modules don't have, can be done with include
and extend togheter. So we would need another method that does both include
and extend (call it inherit). Classes can't be used to define a scope.
Modules can't be instanciated, but classes can.

So why not have only one concept that does both class and modules? You may
call this unified concept either class or a module, I'll call it X.

X is capable of extending, including and inheriting, does scoping and be
instanciated.

How does it sound?

regards,
bráulio

--
"Lute pela sua ideologia. Seja um com sua ideologia. Viva pela sua
ideologia. Morra por sua ideologia" P.R. Sarkar

EITA - Educação, Informação e Tecnologias para Autogestão
Blog - Bráulio Bhavamitra
http://eita.org.br

···

On Thu, Jul 18, 2013 at 11:02 AM, Bráulio Bhavamitra <braulio@eita.org.br>wrote:
--
"Lute pela sua ideologia. Seja um com sua ideologia. Viva pela sua
ideologia. Morra por sua ideologia" P.R. Sarkar

EITA - Educação, Informação e Tecnologias para Autogestão