Linked by Eugenia Loli on Fri 28th Jul 2006 18:28 UTC
Permalink for comment 147152
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/24/13 22:33 UTC
Linked by Howard Fosdick on 05/24/13 21:41 UTC
Linked by Thom Holwerda on 05/24/13 14:44 UTC
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
More News »
Sponsored Links



Member since:
2006-07-28
I believe operator overloading was specifically avoided in Java because it's simply bad style, in most situations, and even when it's not it's often abused.
But then you start using BigInteger or BigDecimal and realize that non-operator overloading is bad style. Bad style and abuse is indicative of bad developers, not operator overloading.