[#4766] Wiki — "Glen Stampoultzis" <trinexus@...>

21 messages 2000/09/04
[#4768] RE: Wiki — "NAKAMURA, Hiroshi" <nahi@...> 2000/09/04

Hi, Glen,

[#4783] Re: Wiki — Masatoshi SEKI <m_seki@...> 2000/09/04

[#4785] Re: Wiki — "NAKAMURA, Hiroshi" <nakahiro@...> 2000/09/05

Howdy,

[#4883] Re-binding a block — Dave Thomas <Dave@...>

16 messages 2000/09/12

[#4930] Perl 6 rumblings -- RFC 225 (v1) Data: Superpositions — Conrad Schneiker <schneik@...>

Hi,

11 messages 2000/09/15

[#4936] Ruby Book Eng. translation editor's questions — Jon Babcock <jon@...>

20 messages 2000/09/16

[#5045] Proposal: Add constants to Math — Robert Feldt <feldt@...>

15 messages 2000/09/21

[#5077] Crazy idea? infix method calls — hal9000@...

This is a generalization of the "in" operator idea which I

17 messages 2000/09/22

[#5157] Compile Problem with 1.6.1 — Scott Billings <aerogems@...>

When I try to compile Ruby 1.6.1, I get the following error:

15 messages 2000/09/27

[ruby-talk:4775] Re: Module vs. Class

From: matz@... (Yukihiro Matsumoto)
Date: 2000-09-04 09:30:45 UTC
List: ruby-talk #4775
Hi,

In message "[ruby-talk:4774] Module vs. Class"
    on 00/09/04, Jilani Khaldi <jilanik@tin.it> writes:

|when it is more convenient to use module than classes, seen classes can
|handle every thing that modules do (IMHO)?
|Thanks.

Two purpose; to provide merely a namespace, and to implement mix-in.

Module is a superclass of Class.  And modules cannot:

  * be inherited
  * instantiate an object

But they can be included from other classes/modules, where classes
cannot be included.

FYI, module inclusion is the only way to implement multiple
inheritance in Ruby.

							matz.

In This Thread