Why modules solve multiple inheritance in Ruby - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to include a module in a class.

Ruby

module Greetings
  def hello
    puts 'Hello!'
  end
end

class Person
  [1] Greetings
end

p = Person.new
p.hello

Drag options to blanks, or click blank then click option'

Ainclude

Bextend

Cinherit

Drequire

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'extend' instead of 'include' to add instance methods.

In Ruby, include is used to mix in a module's methods as instance methods in a class.

2fill in blank

medium

Complete the code to call a method from a module mixed into a class.

Ruby

module Logger
  def log(message)
    puts "Log: #{message}"
  end
end

class App
  include Logger

  def run
    [1]('Application started')
  end
end

app = App.new
app.run

Drag options to blanks, or click blank then click option'

Alog

Bprint

Cputs

Dmessage

Attempts:

3 left

💡 Hint

Common Mistakes

Trying to call puts instead of the module method log.

The method log is defined in the module and becomes available as an instance method in the class.

3fill in blank

hard

Fix the error in the code to correctly use multiple modules in a class.

Ruby

module A
  def greet
    puts 'Hello from A'
  end
end

module B
  def greet
    puts 'Hello from B'
  end
end

class Person
  include A
  [1] B
end

p = Person.new
p.greet

Drag options to blanks, or click blank then click option'

Arequire

Binclude

Cextend

Dinherit

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'extend' for the second module causing method to be unavailable as instance method.

To mix in multiple modules as instance methods, use include for each module.

4fill in blank

hard

Fill both blanks to define a module and include it in a class to solve multiple inheritance.

Ruby

module [1]
  def info
    puts 'Info from module'
  end
end

class Device
  [2] InfoModule
end

d = Device.new
d.info

Drag options to blanks, or click blank then click option'

AInfoModule

Binclude

Cextend

DModuleInfo

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'extend' instead of 'include' to add instance methods.

Define the module with the correct name and include it in the class to add instance methods.

5fill in blank

hard

Fill all three blanks to create two modules and include both in a class to simulate multiple inheritance.

Ruby

module [1]
  def feature_a
    puts 'Feature A'
  end
end

module [2]
  def feature_b
    puts 'Feature B'
  end
end

class Gadget
  [3] FeatureA
  [3] FeatureB
end

g = Gadget.new
g.feature_a
g.feature_b

Drag options to blanks, or click blank then click option'

AFeatureA

BFeatureB

Cinclude

Dextend

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'extend' instead of 'include' causing methods to be class methods.

Define two modules and include both in the class to add their methods as instance methods, simulating multiple inheritance.

Practice

1. Why do Ruby modules help solve the problems of multiple inheritance?

easy

A. They allow sharing methods without inheriting from multiple classes.

B. They force classes to inherit from only one parent class.

C. They prevent any code reuse between classes.

D. They replace the need for classes entirely.

Solution

1. Step 1: Understand multiple inheritance problems

   Multiple inheritance can cause confusion when two parent classes have methods with the same name, leading to conflicts.

2. Step 2: How modules solve this

   Modules let you add shared methods to classes without inheriting from multiple classes, avoiding conflicts and keeping code simple.

3. Final Answer:

   They allow sharing methods without inheriting from multiple classes. -> Option A

4. Quick Check:

   Modules share code without multiple inheritance conflicts = D [OK]

Hint: Modules add methods without multiple inheritance issues [OK]

Common Mistakes:

• Thinking modules replace classes
• Believing modules prevent code reuse
• Confusing modules with single inheritance

2. Which of the following is the correct way to include a module Flyable into a class Bird in Ruby?

easy

A. class Bird; extend Flyable; end

B. class Bird; include Flyable; end

C. class Bird; inherits Flyable; end

D. class Bird; use Flyable; end

Solution

1. Step 1: Recall module inclusion syntax

   In Ruby, to add instance methods from a module to a class, you use include ModuleName.

2. Step 2: Check each option

   class Bird; include Flyable; end uses include Flyable, which is correct. class Bird; inherits Flyable; end uses inherits which is invalid syntax. class Bird; extend Flyable; end uses extend, which adds methods as class methods, not instance methods. class Bird; use Flyable; end uses use, which is not Ruby syntax.

3. Final Answer:

   class Bird; include Flyable; end -> Option B

4. Quick Check:

   Use include to add module methods as instance methods = C [OK]

Hint: Use include to add module methods to instances [OK]

Common Mistakes:

• Using extend instead of include for instance methods
• Using invalid keywords like inherits or use
• Confusing class and instance method inclusion

3. What will be the output of this Ruby code?

module Talkative
  def speak
    "Hello!"
  end
end

class Person
  include Talkative
end

p = Person.new
puts p.speak

medium

A. Hello!

B. NoMethodError

C. nil

D. SyntaxError

Solution

1. Step 1: Understand module inclusion

   The module Talkative defines a method speak. The class Person includes this module, so instances of Person get the speak method.

2. Step 2: Check method call and output

   Creating a new Person instance and calling p.speak will return "Hello!" which is printed by puts.

3. Final Answer:

   Hello! -> Option A

4. Quick Check:

   Included module methods are available to instances = B [OK]

Hint: Included module methods become instance methods [OK]

Common Mistakes:

• Expecting NoMethodError because of missing inheritance
• Confusing extend with include
• Thinking module methods are class methods by default

4. Identify the error in this Ruby code that tries to use a module for multiple inheritance:

module Swimmable
  def swim
    "Swimming"
  end
end

class Animal
  include Swimmable
  include Flyable
end

medium

A. Modules cannot define instance methods.

B. You cannot include more than one module in a class.

C. The module Flyable is not defined, causing a NameError.

D. The include keyword is misspelled.

Solution

1. Step 1: Check module definitions

   The code defines Swimmable but does not define Flyable.

2. Step 2: Understand include behavior

   Including an undefined module like Flyable causes a NameError because Ruby cannot find it.

3. Final Answer:

   The module Flyable is not defined, causing a NameError. -> Option C

4. Quick Check:

   Undefined module inclusion causes NameError = A [OK]

Hint: Always define modules before including them [OK]

Common Mistakes:

• Thinking multiple includes are not allowed
• Believing modules can't have instance methods
• Ignoring undefined module errors

5. Given two modules Readable and Writable both defining a method access, how can you use modules in a class FileHandler to avoid method conflicts and still use both functionalities?

hard

A. Use extend on both modules to add methods as instance methods.

B. Inherit from both modules directly to combine methods.

C. Include only one module and ignore the other.

D. Include both modules and override access in the class to choose behavior.

Solution

1. Step 1: Understand method conflicts with modules

   When two modules define the same method, including both causes the last included module's method to override the previous one.

2. Step 2: Resolve conflict by overriding in class

   To use both, include both modules and define access in FileHandler to decide which module's method to call or combine their behavior.

3. Final Answer:

   Include both modules and override access in the class to choose behavior. -> Option D

4. Quick Check:

   Override conflicting methods in class after including modules = A [OK]

Hint: Override conflicting methods in class after including modules [OK]

Common Mistakes:

• Trying to inherit from modules (not allowed)
• Ignoring method conflicts causing unexpected behavior
• Using extend instead of include for instance methods