module

[Lorem Ipsum]

I am facing some confusion as to what the 'module' keyword does in RGSS. Could somebody explain it to me?

 

[khmp]

module is the superclass/parent to class. Remember that in Ruby almost everything is an object. Not sure enough to say everything. Anyway you can treat them just as you would classes. But in front of method names you would place "self." or "Module_Name" where module name was, well the name of the module. For example:

module Toaster
  def self.toast(bread)
    return bread.toasted
  end
end

Please check here as well: http://www.ruby-doc.org/docs/ProgrammingRuby/  Look up Module.

Good luck with it Lorem Ipsum! :thumb:

 

[Prexus]

Modules are great for naming conventions. Like, if khmp, SephirothSpawn, and I are all making scripts that you use, and we all use constants that have similar names, and there is a risk of overlapping, we can hold our constants in Modules.

like, for example:

module Prexus
  LOLCHEESE = 'HAH'
end
module khmp
  LOLCHEESE = 'ROFL'
end

khmp::LOLCHEESE     #=> 'ROFL'
Prexus::LOLCHEESE     #=> 'HAH'

 

[e]

Basically, modules are abstract classes; in other words, they are EXACTLY the same as classes, except that you can NEVER use the new method on them; thus you do not need to define a initialize method.

Furthermore, with modules, you can have multiple inheritance (in the forms of Mix-Ins). Basically, when you create a new class, and you want it to be a subclass ( a children of, say, Window ), you'd do :

class Window_MyWindow < Window

end

Unfortunately, you CANNOT do something like :

class Window_MyWindow < Window < OtherWindow

end

You can only extend from one class. A way to circumvent that is to use a module.

module OtherWindow
# Methods
end

class Window_MyWindow < Window
include OtherWindow

end

Read Ruby's Pragmatic book. It's available for free. And if you feel adventurous, read Why's (poignant) Guide to Ruby.

 

[khmp]

Basically, modules are abstract classes; in other words, they are EXACTLY the same as classes, except that you can NEVER use the new method on them; thus you do not need to define a initialize method.

My apology there is no initialize so I will correct my original post. Thanks etheon for bringing that to my attention.

 

[e]

Oh. I hadn't read your post anyway. I'll pretend I didn't read this one either  :wink: