commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Henri Yandell <bay...@generationjava.com>
Subject Re: [collections] ArrayIterator
Date Thu, 20 Jun 2002 02:54:37 GMT
Constructor overloaded. I chose to throw some RuntimeExceptions if the
arguments passed in are illegal [ArrayOutOfBoundsException if they pass in
an index outside the array or IllegalArgumentException if the start index
is >= the end index..]

Let me know if those Exceptions are -1'd by anyone.

Hen

On Tue, 18 Jun 2002, Henri Yandell wrote:

>
>
> On Tue, 18 Jun 2002, Michael A. Smith wrote:
>
> > no objections to overloading the constructors.  I'm a bit concerned
> > about the setArray method though.  I don't think it should exist in the
> > first place, and adding more just makes it worse in my opinion -- you
> > sholdn't be able to change the underlying array while iterating because
> > it will result in unpredictable behavior.  Using an empty constructor
> > and a setArray is analogous to making the ArrayIterator a bean, but an
> > iterator should not be a bean -- it's not data.  Just my opinion I
> > guess...
>
> I'm +1 on not having the setArray [though I guess we have to deprecate it
> etc]. Will just overload the constructor.
>
> Hen
>
>
> --
> To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>
>
>


--
To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>


Mime
View raw message