| ConcurrentModificationException | ConcurrentModificationException 2003-07-15 - By peter reilly
We could revert the change, but it does seem dubious to
rely on using undefined behaviour.
Peter
On Tue, 2003-07-15 at 07:47, Stefan Bodewig wrote:
> On Mon, 14 Jul 2003, Adam Jack <ajack@(protected)> wrote:
>
> > As such, I can't understand why/how this code ever works/worked, yet
> > it has -- for quite a while.
>
> The answer is that we used Vector#elements instead of Vector#iterator
> until some time last week - and while Iterator is fail-fast and
> generates the Exception you see, the Enumeration is not (but its
> behavior is not well defined).
>
> We'll have to give the case of the pseudo-target for top-level tasks
> in combination with <import> another thought, I guess.
>
> Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@(protected)
> For additional commands, e-mail: user-help@(protected)
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@(protected)
For additional commands, e-mail: user-help@(protected)
|
|
 |
