Re: hashCode
On 8/11/2012 10:29 PM, Arne Vajh??j wrote:
On 8/11/2012 10:15 PM, Arne Vajh??j wrote:
This is a classic test question in basic Java SE. And that returning
a constant is correct but not smart should be in most Java SE
text books.
Effective Java / Joshua Bloch:
<quote>
// The worst possible legal hash function - never use!
public int hashCode() { return 42; }
It is legal because it ensures that equal objects have the
same hash code. It's atrocious because ...
</quote>
Java 2 SUN Certified Programmer & Developer / Kathy Sierra & Bert Bates:
<quote>
A hashCode() that returns the same value for all instances whether
they're equal or not is still a legal - even appropriate - hashCode()
method! For example,
public int hashCode() {
return 1492;
}
would not violate the contract
...
This hashCode() method is horrible inefficient, ...
...
Nontheless, this one-hash-fits-all method would be
considered appropriate and even correct because it
doesn't violate the contract. Once more, correct does
not necessarily mean good.
</quote>
All this means is that people know how to describe a "correct"
hashCode(), but nobody knows how to describe a "usable" hashCode()
in terms that apply testably to all circumstances.
The O.P. asked whether it would "be potentially better" if
Object's hashCode() returned a constant. He did *not* ask whether
such an implementation would be correct; he only asked if it would
"be potentially better." Upon prompting he explained what he
meant by "better," and in light of that explanation the answer
to his original question is NO. Discussions about "Oh, but it's
CORRECT" are just red herrings; it's still not "better."
--
Eric Sosman
esosman@ieee-dot-org.invalid