- Prioritized List of Improvements
- Highlights of User Feedback

Name of Reviewer: | Ray Ortigas
Current Trail Author(s): | Josh Bloch
Was the author contacted? | Yes If yes, Date: 13 Aug 1999
Comments:

#### Prioritized List of Improvements/Corrections:

Priority Scale:
(1-5)

1 = immediate attention required
3 = fix in next public push (2-3 weeks)
5 = when you get a chance...

1. At the following statement needs to be clarified:

   "The arrays returned by the Collection-views' toArray operations contains the keys, values, or entries in order."

   The keys and entries are sorted by key, as expected, but so are the values. That is, the values are not ordered by value, but according to the keys to which they're matched. The above statement seems to indicate that the values array returned will be ordered by value.

   This has been brought to Josh's attention.

   priority (1-5): 3

2. At I'm still having problems understanding this:

   "[SortedMap provides a constructor] that takes a SortedMap and returns a new SortedMap containing the same mappings as the given SortedMap, and sorted according to the same Comparator (or using the elements' natural ordering, if the specified SortedMap did too). Note that it is the compile-time type of the argument that determines whether this constructor is invoked in preference to the ordinary Map constructor, and not its runtime type!"

   This has been brought to Josh's attention. priority (1-5): 4

3. A user noted that the following sentence at is misleading.

   "The fact that the new implementations are unsynchronized represents a break with the past: Vector and Hashtable were synchronized in versions of the JDK prior to 1.2."

   This sentence seems to indicate that Vector and Hashtable are no longer synchronized.

   This has been brought to Josh's attention.

   priority (1-5): 4

4. Recommendation4
   description
   priority (1-5):

#### Highlights of User Feedback:

- Date:
  User1's email

- Date:
  User2's email

- Date:
  User3's email

- Date:
  User4's email