Why do Rubyists generally hold a number of classes within a module?
cheers
aidy
Say you had a class called "Document", there is already a class called
"Document", so you need to differentiate between the two, so you put them in
separate modules. So then "MODULE1::Document" is different from
"MODULE2::Document".
···
On 28/05/07, aidy.lewis@googlemail.com <aidy.lewis@googlemail.com> wrote:
Why do Rubyists generally hold a number of classes within a module?
cheers
aidy
If you're working on a library to do X, and I'm working on a library
to do Y, and someone else wants to use both libraries in his
application; if we each put our code inside XStuff and YStuff,
respectively, then he won't have to worry about whether we both use a
class named Foo for unrelated purposes. Otherwise, the open classes in
ruby would mean that one definition might trounce parts of another and
neither one would likely work correctly except by luck.
There are other reasons for putting classes in a module, but this is
likely the main one. (Although there are other uses for modules as
well -- especially for use as mixins).
···
On May 28, 10:31 am, "aidy.le...@googlemail.com" <aidy.le...@googlemail.com> wrote:
Why do Rubyists generally hold a number of classes within a module?
--
Regards,
John Wilger