Overloading and Smooth Operators

An anonymous reader writes "IBM DeveloperWorks has an interesting article on operator ad hoc polymorphism (operator overloading for the uninitiated). With the increase in Java popularity and their banning of operator overloading (among other things) the author decides to show some of the great benefits that operator overloading can bring, as long as it is served with a 'healthy dose of caution.'"

Comments

Useful? Doubtful.

[crow]

Sure, there are lots of things you can do with operator overloading, but there are good reasons to avoid them. Ultimately, it comes down to some basic questions:

Will the use of overloading operators...

*) reduce developement time?
*) reduce the number of bugs?
*) improve maintainability?

In most cases, the answer is at best murky. Sure, if you're doing mathematical programming, adding complex numbers, rational numbers (tracking numerators and denominators instead of using floats), or something like that, then it's intiutively a good thing. But in most cases, it's not intuitive. When someone else comes to the project and tries to figure out what's going on, it's like having a bunch of extra macros for them to look up. Function calls make it much more obvious what's going on.

A++ and ++A are NOT the same

[GaelTadh]

Contrary to the article that states that a++ and ++a can be aliased to one call a.next() this is not how it should be done:
a++ needs to return the value of a BEFORE it is incremented
++a needs to return the value of a AFTER it is incremented
Sorry for the rant, I've just spent too long working with programmers that didn't know the difference
(Not at my current job mind you ...)

Re:comp.java.lang.programmer 2001

[Short Circuit]

When did you last take a Physics class? Adding points (or non-C++ vectors) is a very, very common thing.

It's extremely useful for solving, i.e. the following two problems.

• You have four masses of 1 kg each, at (0,3), (2,-1), (4,0) and (2,7). Where is your center of mass?
• John, Jude and July are walking home from work. John lives one block north of his workplace. Jude lives two blocks north and one block east of John. July lives four blocks west of Jude. How many blocks east, and how many blocks north, does July live from work?

...And those are pretty mundane examples. There're more.

Like any tool

[RingDev]

Used poorly, it results in crap. But does that mean that we should block off entire development tool from programmers?

A properly designed and applied overloaded operator can be a great tool for development.

A poorly designed or inappropriatly applied overloaded operator can create a mess of code and a maintenance nightmare.

Now, replace "overloaded operator" with a blank and fill it in with what ever you like. "data layer", "abstract class", "architexture", etc... But if the powers that be decide that programmers need to be protected from data access, inheritance, and design fundamentals, what the hell are we left with?

-Rick