Engineering Full Stack Apps with Java and JavaScript
Both Enumeration and Iterator are interfaces in Java for getting successive elements. Enumeration is older while iterator was introduced later with some improvements. So it is preferred to use Iterator, but we will see Enumeration as well quickly.
Enumeration interface has two methods:
hasMoreElements()
nextElement()
Iterators differ from enumerations by adding an optional remove operation, and having shorter method names.
Methods of Iterator are:
hasNext()
next()
remove()
Iterator is the super interface for the Collection interface.
The Iterable interface with only one method for returning an Iterator.
Iterator is considered more secure and safe because it does not allow other thread to modify the collection object while some thread is iterating over it and throws ConcurrentModificationException in such cases.
ArrayList implements Collection interface, which extends Iterable interface:
List<String> list = new ArrayList<String>();
list.add("one");
list.add("two");
list.add("three");
Using Iterator we can Iterate the list as:
Iterator it = list.iterator();
while(it.hasNext())
{
System.out.println(it.next());
}
This is because ArrayList implements Iterable and has the iterator() method available.
You can also directly use an Iterable implementation in the enhanced for loop without explicitely creating an Iterator:
for(String s:list)
{
System.out.println(s);
}
Iterator has taken the place of Enumeration in the Java collections framework.
Iterator is considered more secure and safe.
Java Specification recommends new implementations to consider using Iterator in preference to Enumeration as the functionality of Enumeration interface is duplicated by the Iterator interface with major improvements.
Enumerations might be faster compared to Iterators due to their read only nature. Still it would be better to go with Iterators as it is the Java recommendation. StringTokenizer is one method in Java that still uses Enumeration.
ListIterator is a sub-interface of Iterator.
ListIterator allows the programmer to traverse the list in either direction, modify the list during iteration, and obtain the iterator's current position in the list.
A ListIterator has no current element; its cursor position always lies between the element that would be returned by a call to previous() and the element that would be returned by a call to next().
The java.util.List has a listIterator() method that returns a listIterator over the elements in this list (in proper sequence).
Methods of a ListIterator are:
add(E e)
hasNext()
hasPrevious()
next(), returns E
nextIndex()
previous(), returns E
previousIndex()
remove()
set(E e)
Note that E is a generic type and any type can be specified.
Comments
Iterator method in the Iterable interface
I know Iterator is an interface and which has 3 methods mentioned above. I saw the java source code as,
public interface Iterable<T> {
Iterator<T> iterator();
}
Here we define an iterator method and its type is the interface Iterator<T>. I see, in the class " AbstractList " it is implemented as,
public Iterator<E> iterator() {
return new Itr();
}
Here we are creting an object of "AbstractList " and reference pointing to the interface "Iterator". why we pointing the reference to an interface, eventhough the "AbstractList " implementing List interface, when we call collection.iterator, we can execute only 3 mthods defined in the Iteratoe interface. is this the way of restricting us from executing methods of List interface? what is the use of keeping object reference to an interface?
I am really confused with pointing the object reference to interface, Heartin please help me to get a clarification on this