Hi,
I know its one of the very common question in every java programmers mind. We all know the diff between interface and abstract class.
Can any one explain me when i have to choose interface / abstract class when i am doing my design??
Welcome to the Java Programming Forums
The professional, friendly Java community. 21,500 members and growing!
The Java Programming Forums are a community of Java programmers from all around the World. Our members have a wide range of skills and they all have one thing in common: A passion to learn and code Java. We invite beginner Java programmers right through to Java professionals to post here and share your knowledge. Become a part of the community, help others, expand your knowledge of Java and enjoy talking with like minded people. Registration is quick and best of all free. We look forward to meeting you.
>> REGISTER NOW TO START POSTING
Members have full access to the forums. Advertisements are removed for registered users.
LinkBack URL
About LinkBacks
Interfaces Vs Abstract classes
Hi,
I know its one of the very common question in every java programmers mind. We all know the diff between interface and abstract class.
Can any one explain me when i have to choose interface / abstract class when i am doing my design??
Related threads:
Re: Interfaces Vs Abstract classes
When you only have methods that you know need to be implemented, use an interface. ActionListeners all must implement the actionPerformed() function, but each implementation is going to be different, so it's an interface.
When you have a partial class that you need to "fill in" with implementations of certain methods, or if you do not want a class to be instantiable, use an abstract class. An AbstractList is an example of this.
Useful links: How to Ask Questions the Smart Way | Use Code Tags | Java Tutorials
Static Void Games - Play indie games, learn from game tutorials and source code, upload your own games!
Reply With Quote