Logan Shaw wrote:
...
Is there a reason why an enhanced for loop couldn't be built to use
either
an Iterator or an Iterable?
There are cases when we have a priori that an Iterator object exists.
For example, some API returns an Iterator. (There are other legit uses.)
In those cases, it would nice to be able to use the object at hand.
...
Here's a solution that I just worked out for my own use:
import java.util.Iterator;
/**
* Iterable whose iterator() method returns a
* specified Iterator.
* @param <T> The base type of the Iterator and Iterable.
*/
public class IteratorToIterable<T> implements Iterable<T> {
private Iterator<T> base;
/**
* Create an Iterable whose iterator method returns base.
* @param base
*/
public IteratorToIterable(Iterator<T> base){
this.base = base;
}
/**
* Get the Iterator passed to the constructor. The Iterator
* should be used only once.
*/
public Iterator<T> iterator() {
return base;
}
}
(1) That is clever, it hurts my brain, AND IT WORKS.
(2) IteratorToIterable is wordy. How about "Reiteration"? :-)