|An abstract class can provide complete, default code and/or just the details that have to be overridden.||An interface cannot provide any code at all,just the signature.|
|In case of abstract class, a class may extend only one abstract class.||A Class may implement several interfaces.|
|An abstract class can have non-abstract methods.||All methods of an Interface are abstract.|
|An abstract class can have instance variables.||An Interface cannot have instance variables.|
|An abstract class can have any visibility: public, private, protected.||An Interface visibility must be public (or) none.|
|If we add a new method to an abstract class then we have the option of providing default implementation and therefore all the existing code might work properly.||If we add a new method to an Interface then we have to track down all the implementations of the interface and define implementation for the new method.|
|An abstract class can contain constructors||An Interface cannot contain constructors|
|Abstract classes are fast.||Interfaces are slow as it requires extra indirection to find corresponding method in the actual class.|
2.When should I use abstract classes and when should I use interfaces?
Use Interfaces when…
- You see that something in your design will change frequently.
- If various implementations only share method signatures then it is better to use Interfaces.
- you need some classes to use some methods which you don't want to be included in the class, then you go for the interface, which makes it easy to just implement and make use of the methods defined in the interface.
Use Abstract Class when…
- If various implementations are of the same kind and use common behavior or status then abstract class is better to use.
- When you want to provide a generalized form of abstraction and leave the implementation task with the inheriting subclass.
- Abstract classes are an excellent way to create planned inheritance hierarchies. They're also a good choice for nonleaf classes in class hierarchies.