Abstract method vs overloading

[tcstcs]

When we have method overriding, what is the use of having abstract methods?

[basha2013]

Hi ,
In the project implementation , it is dificult to verify the code whenever we use our own method names. That why,to usersatnd the code easyly the team leaders creat a some interfaces and declare some required abstract method in side interfaces withe meaningfull method names and fource to develpers create a classes which are subclass to provided interfaces. In this senario we are using method overriding to provide the implementains to abstract methods in implementation classes of interfaces.

[tcstcs]

I am not convinced with ur answer

[nambill]

Abstract methods/classes leave detailed implementation to sub classes, and every sub classes may implement differently, thus leads to polymorphism in OOP.

[helloworld922]

Consider a base class shape. This class has an area method. How would you implement the area method? It's not really practical to do so, so you declare the method abstract and force extending classes to implement the area method.

Could you make shape implement a "dummy" area method which did something like return 0? Yeah, but why? This leads to potentially erroneous results if another class, say Rectangle, doesn't override the area method. Now all of a sudden every Rectangle has area 0 and you're left with a runtime/logic error, the most difficult type of program error to debug. It may even go unnoticed and end up in the wild.

It's a design choice to force extending classes to implement abstract methods. The end goal is to make programming easier, faster, and less buggy. If you force another programmer to implement the area method they're more likely do so up front (since the program won't compile without it). There's no guarantees that it will be implemented correctly, but at least one potential source of problems (missing overriding method) is not the culprit.