Help coderanch get a
new server
by contributing to the fundraiser
  • 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 Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Interface Vs Abstract class

 
Ranch Hand
Posts: 60
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Can anybody tell me in Java, exactly in what kind of situation we have to use interface & not an abstract class?
The typical answer is to achieve multiple Inheritance?
But practically is it the only anwer for that?
 
Greenhorn
Posts: 21
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Parag S. Kulkarni:
Can anybody tell me in Java, exactly in what kind of situation we have to use interface & not an abstract class?
The typical answer is to achieve multiple Inheritance?
But practically is it the only anwer for that?



Besides this, there is another answer also. That when u implement an interface in several unrelated classes, u can interact with these two classes although there is no physical connection between those(viz. subclass/parent-child relationship). In fact here the term interface comes into existence. It is the interface between two unrelated classes so that they can communicate.
Is it satisfactory?
 
Greenhorn
Posts: 15
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The purpose of an interface is to define only the structure but not the implementation of a class. This is used to define the WHAT and leave the HOW to the implementing class.
But an abstract class can have a partial implementation.
 
Ranch Hand
Posts: 5093
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
more correctly, an interface defines behaviour through a contract while an abstract class defines a relation through inheritance.

There are theoretical as well as practical differences between the two.

Saying you implement an interface tells calling classes that "yes, I know how to do this".
Inheriting from an abstract class says "yes, I AM an XXX and therefore I will indeed know how to do this".
It's a far stronger link.
 
Oh sure, it's a tiny ad, but under the right circumstances, it gets bigger.
We need your help - Coderanch server fundraiser
https://coderanch.com/t/782867/Coderanch-server-fundraiser
reply
    Bookmark Topic Watch Topic
  • New Topic