Doug Lea writes:

To prevent misunderstandings like one that just happened to someone
at Google, can we insert "optionally" in class spec about Iterator.remove,
as below?

Thanks!

-Doug


Index: AbstractQueue.java
===================================================================
RCS file: /export/home/jsr166/jsr166/jsr166/src/main/java/util/AbstractQueue.java,v
retrieving revision 1.34
diff -c -r1.34 AbstractQueue.java
*** AbstractQueue.java 28 May 2006 23:36:29 -0000 1.34
--- AbstractQueue.java 3 Nov 2006 14:47:29 -0000
***************
*** 20,26 ****
   * minimally define a method {@link Queue#offer} which does not permit
   * insertion of <tt>null</tt> elements, along with methods {@link
   * Queue#peek}, {@link Queue#poll}, {@link Collection#size}, and a
! * {@link Collection#iterator} supporting {@link
   * Iterator#remove}. Typically, additional methods will be overridden
   * as well. If these requirements cannot be met, consider instead
   * subclassing {@link AbstractCollection}.
--- 20,26 ----
   * minimally define a method {@link Queue#offer} which does not permit
   * insertion of <tt>null</tt> elements, along with methods {@link
   * Queue#peek}, {@link Queue#poll}, {@link Collection#size}, and a
! * {@link Collection#iterator} optionally supporting {@link
   * Iterator#remove}. Typically, additional methods will be overridden
   * as well. If these requirements cannot be met, consider instead
   * subclassing {@link AbstractCollection}.