毕业论文外文译-Effectjava.doc

外文资料 《Effect java》 1.Always Override HashCode When You Override Equals A common source of bugs is the failure to override the hashCode method. Yo u must override hashCode in every class that overrides equals.Failure to do so will result in a violation of the general contract for Object.hashCode, which will prevent your class from functioning properly in conjunction with all hash-based collections, including HashMap ,HashSet, and Hashtable. Here is the contract, copied from the Object specification [JavaSE6]: (1) Whenever it is invoked on the same object more than once during an execution of an application, the hashCode method must consistently return the same integer, provided no information used in equals comparisons on the object is modified. This integer need not remain consistent from one execution of an application to another execution of the same application. (2) If two objects are equal according to the equals(Object) method, then calling the hashCode method on each of the two objects must produce the same integer result. (3) It is not required that if two objects are unequal according to the equals(Object) method, then calling the hashCode method on each of the two objects must produce distinct integer results. However, the programmer should be aware that producing distinct integer results for unequal objects may improve the performance of hash tables. The key provision that is violated when you fail to override hashCode is the second one: equal objects must have equal hash codes.Two distinct instances may be logically equal according to a class’s equals method, but to Object’s hashCode method, they’re just two objects with nothing much in common. Therefore Object’s hashCode method returns two seemingly random numbers instead of two equal numbers as required by the contract. 2.Always Override toString While java.lang.Object provides an implementation of the toString method, the string that it returns is generally not what the user of your