mirrors/gcc
0
0
Fork 0
mirror of https://gcc.gnu.org/git/gcc.git synced 2024-12-11 21:03:45 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity

BitSet.java: Updated @specnote.

Browse Source 
2000-10-30  Bryce McKinlay  <bryce@albatross.co.nz>

	* java/util/BitSet.java: Updated @specnote.

From-SVN: r37138
This commit is contained in:
Bryce McKinlay 2000-10-30 01:51:34 +00:00 committed by Bryce McKinlay
parent 23d3495f45
commit 661a98d17a
2 changed files with 10 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
libjava/ChangeLog
View File

@ -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

17
libjava/java/util/BitSet.java
View File

@ -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>