• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Bear Bibeault
  • Devaka Cooray
  • Liutauras Vilda
  • Jeanne Boyarsky
  • Knute Snortum
  • Junilu Lacar
  • paul wheaton
Saloon Keepers:
  • Ganesh Patekar
  • Frits Walraven
  • Tim Moores
  • Ron McLeod
  • Carey Brown
  • Stephan van Hulst
  • salvin francis
  • Tim Holloway

Difference between abstract class and interface  RSS feed

Posts: 6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
when should i use an abstract class and when should I use an interface
Ranch Hand
Posts: 452
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Here is what i do
If u want to specify partial implementation of ur class make it abstract else make it interface
Ranch Hand
Posts: 78
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Junior
It's a very good question. This is what I understand.
Abstract class is a class which has atleast one abstract method. Here, to get polymorphic behavior, the subclasses have to implement the method.
An interface is a collection of constants and methods. It can contain either constants or methods or both.
Any unrelated class can implement the interface by providing implementations for its abstract methods. So, interface enable you to expediate polymorphism without necessarily defining subclasses.
1. Interface enables you to expediate polymorphism without the need of subclasses. This is not true for abstract class.
This is the major difference between abstract class and an interface.
2. An abstract class can consist other methods too which are not abstract, whereas an interface can contain only abstract methods.
As far as the advantages of Interface goes, you have already mentioned the most important one that we can implement more than one interface but extend only one class.
An interface is also a very handy means of packaging up constants. You can define constants that will be common to all classes and put them together in an interface. Any class that requires it, has to just implement it.
your question:
Why can't abstract classes simply be replaced by interfaces???
From any application point of view, I feel we should use abstract class when we need to restrict the implementation of abstract methods to only those classes which are related.
Use interface when you have methods and constants which can be used by any class in an application. For e.g Date routine method or standard values like pi, or conversion factors like inch to centimeters, etc.
I think i have explained whatever I could think of and I hope it helps you.
High Plains Drifter
Posts: 7292
Netbeans IDE VI Editor
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Junior nka Katerina --
Please take a closer look at our naming policy. We ask that you post using a display that includes a first and last name.
I will close the threads you've created until you've had a chance to make these changes.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!