Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
We have something like
List lst = new LinkedList();
which shows that List is some sort of Class. So, why call it an Interface? We can simply call it an Abstract class which implements Collection.
Interfaces and Abstract classes are used for different purposes. See this question.
A List defines a set of behaviour we want list-type objects to have, not the basis for a hierarchy of data structures. It doesn’t need to specify any shared behaviour or anything like that. It just has the simple job of saying “everything that wants to call itself a List should be able to do these things”