I believe if you search 'abstract classes versus interfaces' here you will get hundreds of hits. Google will return thousands more. This horse has been beaten to death. There is undoubtedly an answer in one of the numerous threads already posted.
If anyone else feels charitable, then by all means chime in. I've retyped this one personally well over a dozen times. And beer, she is a callin'!
- Saish
> What is the exact difference between abstract classes
> and interface in real scenario?
>
> Plz could you give a practical example?
>
> Thanks
One allows you to define behavior, the other implementation that can be extended. If you want a real scenario go look at List and AbstractList.
> At least your head doesn't make a *plonk* sound.
Mine just makes a splutchy bursting watermelon type sound.
To the original poster - to make things simple, if there is any doubt about which you should use, use an interface. If the situation calls for an abstract class, you will know that an interface is the wrong choice, because it will be impossible to do what you want to do with an interface.
Drake