diff options
| author | Bryce McKinlay <bryce@albatross.co.nz> | 2000-10-30 01:51:34 +0000 |
|---|---|---|
| committer | Bryce McKinlay <bryce@gcc.gnu.org> | 2000-10-30 01:51:34 +0000 |
| commit | 661a98d17ace6fdf2aa293528f175e882ac8981c (patch) | |
| tree | 223576160418ba3d5267dc85b9ee15df44965d20 | |
| parent | 23d3495f4523d1ec1ebda70cdf71168238be7898 (diff) | |
| download | gcc-661a98d17ace6fdf2aa293528f175e882ac8981c.zip gcc-661a98d17ace6fdf2aa293528f175e882ac8981c.tar.gz gcc-661a98d17ace6fdf2aa293528f175e882ac8981c.tar.bz2 | |
BitSet.java: Updated @specnote.
2000-10-30 Bryce McKinlay <bryce@albatross.co.nz>
* java/util/BitSet.java: Updated @specnote.
From-SVN: r37138
| -rw-r--r-- | libjava/ChangeLog | 4 | ||||
| -rw-r--r-- | libjava/java/util/BitSet.java | 17 |
2 files changed, 10 insertions, 11 deletions
diff --git a/libjava/ChangeLog b/libjava/ChangeLog index 3a58979..be1a10a 100644 --- a/libjava/ChangeLog +++ b/libjava/ChangeLog @@ -1,3 +1,7 @@ +2000-10-30 Bryce McKinlay <bryce@albatross.co.nz> + + * java/util/BitSet.java: Updated @specnote. + 2000-10-29 Bryce McKinlay <bryce@albatross.co.nz> * java/util/AbstractCollection.java (addAll): Use size() instead of diff --git a/libjava/java/util/BitSet.java b/libjava/java/util/BitSet.java index 5a2dd44..fa0f3a1 100644 --- a/libjava/java/util/BitSet.java +++ b/libjava/java/util/BitSet.java @@ -33,17 +33,12 @@ import java.io.Serializable; * while another thread is simultaneously modifying it, the results are * undefined. * - * @specnote There is some confusion as to whether or not this class should - * be synchronized. JDK 1.1 javadocs explicitly state that the - * class is NOT synchronized, however the code listed in the JDK 1.3 - * javadoc for the hashCode() method implies that it is. It is not - * stated elsewhere in the 1.2 javadoc that the class is - * synchronized, unlike Hashtable and Vector. From an efficiency - * perspective, it is very undesirable to synchronize this class - * because multiple locks and explicit lock ordering are required - * to safely synchronize some methods. For this reason we're going - * with the unsynchronized implementation unless the specs are - * changed to explicitly say otherwise. + * @specnote Historically, there has been some confusion as to whether or not + * this class should be synchronized. From an efficiency perspective, + * it is very undesirable to synchronize it because multiple locks + * and explicit lock ordering are required to safely synchronize some + * methods. The JCL 1.2 supplement book specifies that as of JDK + * 1.2, the class is no longer synchronized. * * @author Jochen Hoenicke * @author Tom Tromey <tromey@cygnus.com> |