Multiple inheritance using interfaces in Java - Time & Space Complexity

Time Complexity: Multiple inheritance using interfaces

O(1)

Understanding Time Complexity

We want to understand how the time needed to run code changes when using multiple inheritance with interfaces in Java.

Specifically, how does calling methods from multiple interfaces affect the program's speed as the input grows?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

interface A {
    void methodA();
}

interface B {
    void methodB();
}

class C implements A, B {
    public void methodA() { System.out.println("A"); }
    public void methodB() { System.out.println("B"); }
}

public class Test {
    public static void main(String[] args) {
        C obj = new C();
        obj.methodA();
        obj.methodB();
    }
}
    

This code shows a class implementing two interfaces and calling their methods.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Calling methods from two interfaces once each.
• How many times: Each method is called exactly once; no loops or recursion.

How Execution Grows With Input

Since there are no loops or repeated calls, the number of operations stays the same no matter how big the input is.

Input Size (n)	Approx. Operations
10	2 method calls
100	2 method calls
1000	2 method calls

Pattern observation: The work does not increase with input size; it stays constant.

Final Time Complexity

Time Complexity: O(1)

This means the time to run the code stays the same no matter how big the input is.

Common Mistake

[X] Wrong: "Using multiple interfaces makes the program slower as input grows because it has more methods to call."

[OK] Correct: The number of method calls here is fixed and does not depend on input size, so the time does not grow with input.

Interview Connect

Understanding how multiple inheritance with interfaces affects time helps you explain design choices clearly and shows you know how code structure relates to performance.

Self-Check

"What if each method called inside the interfaces contained a loop over an input array? How would the time complexity change?"

Practice

1. What is the main reason Java uses interfaces for multiple inheritance instead of classes?

easy

A. To avoid the diamond problem and allow safe multiple inheritance

B. Because Java does not support inheritance at all

C. To make code run faster

D. To prevent any method overriding

Solution

1. Step 1: Understand Java inheritance limitations

   Java does not allow multiple inheritance with classes to avoid ambiguity known as the diamond problem.

2. Step 2: Role of interfaces in multiple inheritance

   Interfaces allow multiple inheritance of type without implementation conflicts, enabling safe multiple inheritance.

3. Final Answer:

   To avoid the diamond problem and allow safe multiple inheritance -> Option A

4. Quick Check:

   Interfaces solve diamond problem = A [OK]

Hint: Interfaces enable multiple inheritance safely in Java [OK]

Common Mistakes:

• Thinking Java supports multiple class inheritance
• Believing interfaces improve speed
• Confusing method overriding prevention

2. Which of the following is the correct syntax for a class Car implementing two interfaces Engine and Wheels?

easy

A. public class Car implements Engine & Wheels {}

B. public class Car extends Engine, Wheels {}

C. public class Car implements Engine, Wheels {}

D. public class Car extends Engine implements Wheels {}

Solution

1. Step 1: Recall Java syntax for implementing multiple interfaces

   Java uses the keyword implements followed by a comma-separated list of interfaces.

2. Step 2: Check each option's syntax

   public class Car implements Engine, Wheels {} correctly uses implements Engine, Wheels. Options B and D incorrectly use extends for interfaces or mix keywords wrongly. public class Car implements Engine & Wheels {} uses an invalid '&' symbol.

3. Final Answer:

   public class Car implements Engine, Wheels {} -> Option C

4. Quick Check:

   Multiple interfaces use comma with implements = A [OK]

Hint: Use 'implements' with commas for multiple interfaces [OK]

Common Mistakes:

• Using extends instead of implements for interfaces
• Using '&' instead of commas
• Mixing extends and implements incorrectly

3. What will be the output of the following code?

interface A {
    default void show() { System.out.println("A"); }
}
interface B {
    default void show() { System.out.println("B"); }
}
class C implements A, B {
    public void show() {
        A.super.show();
        B.super.show();
    }
}
public class Test {
    public static void main(String[] args) {
        C obj = new C();
        obj.show();
    }
}

medium

A. B\nA

B. A\nB

C. Compilation error due to method conflict

D. No output

Solution

1. Step 1: Understand default methods in interfaces

   Both interfaces A and B have a default method show(). Class C implements both and overrides show().

2. Step 2: Analyze method calls inside C's show()

   C's show() calls A.super.show() then B.super.show(), so it prints "A" then "B" on separate lines.

3. Final Answer:

   A B -> Option B

4. Quick Check:

   Calling both interface methods prints A then B [OK]

Hint: Use InterfaceName.super.method() to call specific default methods [OK]

Common Mistakes:

• Expecting compilation error without override
• Confusing order of prints
• Missing super calls causing ambiguity

4. Identify the error in the following code snippet:

interface X {
    void display();
}
interface Y {
    void display();
}
class Z implements X, Y {
    // No display() method implemented
}

medium

A. Class Z must implement display() method or be declared abstract

B. No error, code compiles fine

C. Interfaces cannot have methods with same name

D. Class Z should extend interfaces, not implement

Solution

1. Step 1: Check interface method requirements

   Interfaces X and Y both declare display() method without implementation.

2. Step 2: Check class Z implementation

   Class Z implements both interfaces but does not provide display() method, so it must be abstract or implement the method.

3. Final Answer:

   Class Z must implement display() method or be declared abstract -> Option A

4. Quick Check:

   Implement all interface methods or declare abstract = D [OK]

Hint: Implement all interface methods or declare class abstract [OK]

Common Mistakes:

• Assuming no implementation needed if methods have same name
• Thinking interfaces cannot share method names
• Using extends instead of implements for interfaces

5. Given interfaces Readable and Writable with methods read() and write() respectively, how can you design a class FileHandler that implements both interfaces and provides default logging before each operation? Choose the best approach.

hard

A. Implement both interfaces in FileHandler and override methods to add logging then call interface methods

B. Make FileHandler extend both interfaces and implement methods without logging

C. Use abstract class instead of interfaces for multiple inheritance

D. Implement interfaces and add logging inside overridden methods in FileHandler

Solution

1. Step 1: Understand interface implementation and method overriding

   FileHandler must implement both read() and write() methods from interfaces.

2. Step 2: Add logging before operations

   Override methods in FileHandler to add logging code before performing the actual operation.

3. Step 3: Choose best approach

   Implement interfaces and add logging inside overridden methods in FileHandler correctly describes implementing interfaces and adding logging inside overridden methods. Implement both interfaces in FileHandler and override methods to add logging then call interface methods incorrectly suggests calling interface methods which have no implementation. Make FileHandler extend both interfaces and implement methods without logging uses wrong keyword extend. Use abstract class instead of interfaces for multiple inheritance avoids interfaces and is not best for multiple inheritance.

4. Final Answer:

   Implement interfaces and add logging inside overridden methods in FileHandler -> Option D

5. Quick Check:

   Override interface methods to add behavior = C [OK]

Hint: Override interface methods to add extra behavior like logging [OK]

Common Mistakes:

• Trying to extend interfaces instead of implement
• Calling interface methods directly which have no body
• Using abstract class when interfaces are better for multiple inheritance