Re: Util dependency on Collections?

[Jari Worsley]

[EMAIL PROTECTED] wrote:

> 
>     // does its best to make an iterator for an object.
>     //
>     public static java.util.Iterator getIterator(java.lang.Object);

what's the reasoning behind the above method? what's wrong with the
iterator() method on Collection interface?

Or is the idea that you can pass a single object to it that isn't of
type Collection and still get back an iterator? i.e. be able to treat
any object as a collection - just that single objects are always
Collections of one :)

?
> 
>  // get sub-collection of a collection. need to add an array version too
>     public static java.util.Collection slice(java.util.Collection, int,
> int);
> 

how does the above work with Collections that don't have an explicit
ordering, like a Map or Set?

Jari

--
Jari Worsley
Senior Programmer
Hyperlink Interactive Ltd