Linked by Eugenia Loli on Fri 28th Jul 2006 18:28 UTC
Thread beginning with comment 147273
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
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
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
More News »
Sponsored Links



Member since:
2006-04-02
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.
Infact, Java already has some form of operator overloading. For example, when you write:
String line = "X = " + x + ", Y = " + y;
You begin to realize how useful operator overloading is. Why can't this be extend to other classes (like BigDecimal & BigInteger as mentioned above), or even our own?