Let's continue discussion about hashCode() from thread "Algorithmic tricks".
2006/7/27, Spark Shen <[EMAIL PROTECTED]>:
I do have a concern that in some classes, hash calculation does have very import impact, but in some others may not be so important, or may not be taken so heavy use. IMHO, the 'degree of hashing' provided by this method may be a little too general to use by all classes. It may be too heave for some, but too light for others.
Please give some examples of heavy and light hashing in your vision.
> But only several classes are using it. I suggest integrate HashCode in > all hashCode() implementations (about 200 files), I can do this. Anybody > else can improve HashCode work. > Such a utility class is very helpful, but utilize it in all classes may not be suitable. And do have some 'premature optimization' smell here. As anthon said "What I'm talking about is not related to 'premature optimization' that is now being discussed in another thread but something very narrow, limited to maybe one method and not influencing anything else. "
So your suggestion is leave hashCode as is? --------------------------------------------------------------------- Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
