The key technical differences between an abstract class and an interface are:
public
(they are defined public by default).
An Interface contains only the definition / signature of functionality, and if we have some common functionality as well as common signatures, then we need to use an abstract class. By using an abstract class, we can provide behavior as well as functionality both in the same time. Another developer inheriting abstract class can use this functionality easily, as they would only need to fill in the blanks.
Class example (pseudo code):
// I say all motor vehicles should look like this: interface MotorVehicle { void run(); int getFuel(); } // My team mate complies and writes vehicle looking that way class Car implements MotorVehicle { int fuel; void run() { print("Wrroooooooom"); } int getFuel() { return this.fuel; } }
Abstract example
// I say all motor vehicles should look like this: abstract class MotorVehicle { int fuel; // They ALL have fuel, so lets implement this for everybody. int getFuel() { return this.fuel; } // That can be very different, force them to provide their // own implementation. abstract void run(); } // My teammate complies and writes vehicle looking that way class Car extends MotorVehicle { void run() { print("Wrroooooooom"); } }
Any hardware or software environment in which a program runs, is known as a platform.…
Multi-threading is a Java feature that allows concurrent execution of two or more parts of…
'is a' relationship is also known as inheritance. We can implement 'is a' relationship or…
Constants in java are created using static and final keywords. Constants contains only uppercase letters.…
Variable names should start with small letters. Variable names should be nouns. Short meaningful names…
Method names should start with small letters. Method names are usually verbs If method contains…