Interface vs abstract class vs trait in PHP - Quick Revision & Key Differences

Recall & Review

beginner

What is an interface in PHP?

An interface defines a contract with method signatures but no method bodies. Classes that implement the interface must provide the method implementations.

beginner

What is an abstract class in PHP?

An abstract class can have both method signatures (abstract methods) and method bodies. It cannot be instantiated directly and is meant to be extended by other classes.

beginner

What is a trait in PHP?

A trait is a reusable set of methods that can be included in multiple classes to share functionality without using inheritance.

beginner

Can a PHP class implement multiple interfaces?

Yes, a PHP class can implement multiple interfaces, allowing it to follow multiple contracts.

beginner

Can a PHP class use multiple traits?

Yes, a PHP class can use multiple traits to include different sets of reusable methods.

Which of the following can contain method implementations in PHP?

A Both B and C

B Abstract class

C Trait

D Interface

Abstract classes and traits can contain method implementations, while interfaces only declare method signatures.

Can a PHP interface have properties?

A Only if declared public

B Yes, with default values

C Yes, but only static properties

D No, interfaces cannot have properties

Interfaces cannot have properties; they only declare method signatures.

Which keyword is used to include a trait in a PHP class?

A implements

B extends

C use

D include

The 'use' keyword is used inside a class to include a trait.

Can a PHP class extend multiple abstract classes?

A No, PHP supports only single inheritance

B Yes, but only if abstract classes implement interfaces

C Yes, PHP supports multiple inheritance

D Only if using traits

PHP supports only single inheritance, so a class can extend only one abstract class.

What is the main purpose of traits in PHP?

A To define method signatures

B To share reusable code between classes

C To enforce class contracts

D To replace interfaces

Traits allow sharing reusable methods across classes without using inheritance.

Explain the differences between interfaces, abstract classes, and traits in PHP.

Think about what each one can contain and how they are used in classes.

When would you choose to use a trait instead of an abstract class or interface in PHP?

Consider code reuse and inheritance limitations.

Practice

1. Which of the following best describes a PHP interface?

easy

A. It is used to create objects directly without classes.

B. It allows code reuse by including methods directly into classes.

C. It can contain both implemented and abstract methods to share common behavior.

D. It defines method signatures without implementation, forcing classes to implement them.

Solution

1. Step 1: Understand what an interface is in PHP

   An interface only declares method names without any code, so classes must implement all methods.

2. Step 2: Compare with traits and abstract classes

   Traits provide reusable code, and abstract classes can have both code and abstract methods, unlike interfaces.

3. Final Answer:

   It defines method signatures without implementation, forcing classes to implement them. -> Option D

4. Quick Check:

   Interface = method signatures only [OK]

Hint: Interfaces only declare methods, no code inside [OK]

Common Mistakes:

• Thinking interfaces can have method bodies
• Confusing traits with interfaces
• Believing interfaces can be instantiated

2. Which of the following is the correct syntax to declare a trait in PHP?

easy

A. abstract trait Logger {}

B. interface Logger {}

C. trait Logger {}

D. class Logger {}

Solution

1. Step 1: Recall PHP syntax for traits

   Traits are declared using the keyword trait followed by the trait name and curly braces.

2. Step 2: Eliminate incorrect options

   abstract trait Logger {} is invalid because traits cannot be abstract. interface Logger {} declares an interface, and class Logger {} declares a class.

3. Final Answer:

   trait Logger {} -> Option C

4. Quick Check:

   Trait declaration uses 'trait' keyword [OK]

Hint: Traits start with 'trait' keyword, no 'abstract' needed [OK]

Common Mistakes:

• Adding 'abstract' before trait keyword
• Confusing trait with interface or class syntax
• Using 'class' keyword for traits

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

trait Hello {
    public function sayHello() {
        return "Hello from trait!";
    }
}

abstract class Base {
    abstract public function sayHello();
}

class MyClass extends Base {
    use Hello;
}

$obj = new MyClass();
echo $obj->sayHello();

medium

A. Hello from trait!

B. Fatal error: Class MyClass contains 1 abstract method

C. Hello from Base

D. Syntax error

Solution

1. Step 1: Understand trait usage in class extending abstract

   The trait Hello provides the method sayHello(). The abstract class Base declares sayHello() as abstract.

2. Step 2: Check if MyClass implements abstract method

   MyClass uses the trait which provides the required method, so no error occurs and the method returns the trait's string.

3. Final Answer:

   Hello from trait! -> Option A

4. Quick Check:

   Trait method satisfies abstract method [OK]

Hint: Trait methods fulfill abstract methods if used [OK]

Common Mistakes:

• Expecting fatal error for missing method
• Confusing trait method with abstract class method
• Thinking abstract method must be implemented in class only

4. Identify the error in the following PHP code:

interface Logger {
    public function log(string $msg);
}

trait Logger {
    public function log(string $msg) {
        echo $msg;
    }
}

class FileLogger implements Logger {
    use Logger;
}

medium

A. Trait and interface cannot have the same name.

B. Class cannot implement interface and use trait simultaneously.

C. Trait methods cannot have parameters.

D. Interface methods must have implementation.

Solution

1. Step 1: Check naming conflicts

   Both the interface and trait are named Logger, which causes a fatal error due to name collision.

2. Step 2: Verify other rules

   Classes can implement interfaces and use traits simultaneously. Traits can have parameters in methods. Interface methods cannot have implementation.

3. Final Answer:

   Trait and interface cannot have the same name. -> Option A

4. Quick Check:

   Name collision between trait and interface [OK]

Hint: Trait and interface names must differ [OK]

Common Mistakes:

• Thinking class can't use trait and implement interface
• Believing traits can't have parameters
• Assuming interface methods have code

5. You want to create a PHP class that must implement a method connect() defined by an interface, share common code for disconnect() from an abstract class, and reuse logging code from a trait. Which is the best way to design this?

hard

A. Create an interface with connect() and disconnect(), a trait with logging, and a class that extends the interface and uses the trait.

B. Create an interface with connect(), an abstract class with disconnect(), a trait with logging, then a class that implements the interface, extends the abstract class, and uses the trait.

C. Create an abstract class with connect() and disconnect(), a trait with logging, and a class that implements the trait and extends the interface.

D. Create a trait with connect() and disconnect(), an abstract class with logging, and a class that extends the trait and implements the abstract class.

Solution

1. Step 1: Understand roles of interface, abstract class, and trait

   Interface defines required methods like connect(). Abstract class can provide shared code like disconnect(). Trait is for reusable code like logging.

2. Step 2: Combine them correctly in a class

   PHP allows a class to implement interfaces, extend one abstract class, and use multiple traits. So the class should implement the interface, extend the abstract class, and use the trait.

3. Final Answer:

   Create an interface with connect(), an abstract class with disconnect(), a trait with logging, then a class that implements the interface, extends the abstract class, and uses the trait. -> Option B

4. Quick Check:

   Interface + abstract class + trait combined properly [OK]

Hint: Interface for methods, abstract class for code, trait for reuse [OK]

Common Mistakes:

• Trying to extend multiple classes
• Confusing trait and abstract class roles
• Extending interface instead of implementing