Java Modcount (ArrayList)

Question

In Eclipse, I see that ArrayList objects have a modCount field. What is its purpose? (number of modifications?)

Answer 1

It allows the internals of the list to know if there has been a structural modification made that might cause the current operation to give incorrect results.

If you've ever gotten ConcurrentModificationException due to modifying a list (say, removing an item) while iterating it, its internal modCount was what tipped off the iterator.

The AbstractList docs give a good detailed description.

Answer 2

Yes. If you ever intend to extend AbstractList, you have to write your code so that it adheres the modCount's javadoc as cited below:

/**  * The number of times this list has been <i>structurally modified</i>.  * Structural modifications are those that change the size of the  * list, or otherwise perturb it in such a fashion that iterations in  * progress may yield incorrect results.  *  * <p>This field is used by the iterator and list iterator implementation  * returned by the {@code iterator} and {@code listIterator} methods.  * If the value of this field changes unexpectedly, the iterator (or list  * iterator) will throw a {@code ConcurrentModificationException} in  * response to the {@code next}, {@code remove}, {@code previous},  * {@code set} or {@code add} operations.  This provides  * <i>fail-fast</i> behavior, rather than non-deterministic behavior in  * the face of concurrent modification during iteration.  *  * <p><b>Use of this field by subclasses is optional.</b> If a subclass  * wishes to provide fail-fast iterators (and list iterators), then it  * merely has to increment this field in its {@code add(int, E)} and  * {@code remove(int)} methods (and any other methods that it overrides  * that result in structural modifications to the list).  A single call to  * {@code add(int, E)} or {@code remove(int)} must add no more than  * one to this field, or the iterators (and list iterators) will throw  * bogus {@code ConcurrentModificationExceptions}.  If an implementation  * does not wish to provide fail-fast iterators, this field may be  * ignored.  */ 

Taking a look into the actual JDK source code and reading the javadocs (either online or in code) help a lot in understanding what's going on. Good luck.

I would add, you can add JDK source code to Eclipse so that every F3 or CTRL+click on any Java SE class/method points to the actual source code. If you download the JDK, you should have the src.zip in the JDK installation folder. Now, in Eclipse's the top menu, go to Window » Preferences » Java » Installed JREs. Select the current JRE and click Edit. Select the rt.jar file, click at Source Attachment, click at External File, navigate to JDK folder, select the src.zip file and add it. Now the source code of the Java SE API is available in Eclipse. The JDK source code gives a lot of insights. Happy coding :)