Understanding use of Interface and Abstract class
We know that an interface is defined by the interface keyword and all methods are abstract. All methods declared in an interface must be public; this is simply the nature of an interface. Here is the example :
In an interface the method body is not defined, just the name and the parameters. If we do not use an interface what problems will happen? Why we should use interface? Herein you will get these answers. Please see the code in below:
In the above example I do not use interface. I write to the log using the LogToFile class. But now if I want to write a log using LogToDatabase I have to change hard coded class reference in the above code on line number 23. That line code in below :
public function __construct(LogToFile $logger)
This code will be
public function __construct(LogToDatabase $logger)
In a large project, if I have multiple classes and a need to change, then I have to change all the classes manually. But If we use an interface this problem is solved; and we will not need to change code manually.
Now see the following code and try to realize what happened if I use interface
Now If I change from LogToDatabase to LogToFile I do not have to change the constructor method manually. In the constructor method I have Injected an interface; not any arbitrary class. So If you have multiple classes and swap from one class to another class you will get the same result without changing any class references.
In the above example I write log using LogToDatabase and now I want to write log using LogToFile, I can call in this way
$controller = new UsersController(new LogToFile);
I get result without changing other classes.Because Interface handle this swapping issue.
An abstract class is a class that is only partially implemented by the programmer. It may contains at least one abstract method, which is a method without any actual code in it, just the name and the parameters, and that has been marked as “abstract”.
An abstract method is simply a function definition that serves to tell the programmer that the method must be implemented in a child class.Here is the example :
Now the question is when will the situation that a method will be needed and must be implemented? Here I will try to explain. Please see the Tea class.
Now we look at the coffee class.
In the above two classes, the three methods addHotWater(), addSugar() and addMilk() are same. So we should remove duplicated code. We can do it in the following way :
I make an abstract class and name it Template. Here I define addHotWater(), addSugar() and addMilk(); and make an abstract method named addPrimaryToppings.
Now If I make the Tea class extend the Template class then I will get the three defined methods and must define the addPrimaryToppings() method. In a similar way the coffee class will as well.
And if you’d like to learn more and get code about Interface and Abstract class, please check out my GitHub (stars always appreciated) repository.
Thanks for reading.