Is operator overriding necessary? Should it be avoided?

import java.math.BigInteger; BigInteger x1 = BigInteger.valueOf(3); BigInteger y1 = BigInteger.valueOf(4); BigInteger x2 = BigInteger.valueOf(5); BigInteger y2 = BigInteger.valueOf(6); BigInteger z = x1.multiply(x2).add(y1.multiply(y2)); If the above code drives you mad, you can switch to Scala. // No importing needed val x1: BigInt = 3 val y1: BigInt = 4 val x2: BigInt = 5 val y2: BigInt = 6 val z: BigInt = x1 * x2 + y1 * y2 Or switch to Python x1,y1,x2,y2 = 3,4,5,6 z = x1*x2 + y1*y2 print(2**70) # In Python3, int has unlimited precision. Or switch to Haskell [code] z = x1*x2 + y1*y2 (x1,y1,x2,y2) = (3,4,5,6) -- order doesn't matter -- Operators are functions, too. foldr (+) 0 [1,2,3,4,5,6,7,8,9,10] -- (1+(2+(3+(4+(5+(6+(7+(8+(9+(10+0)))))))))) [/code]

The point is: making things simpler helps you make less mistakes. I proved this in my project that adding a layer of abstraction not only make your life easier, but also make your program more powerful as well. You will be willing to add features which were way too complicated and you were not brave enough to touch. This is the power of abstraction. 【 在 qiukun 的大作中提到: 】 : [size=4]Every operator can be transform to function call. : However, operators, especially the infix ones, provide better readability and save the stack of brain (a infix form can be read from left to right). : But operator overriding did hide details, which may hide problems and increase the difficulty to debug. (Seems that references have the same problem.) : ...................

At present, I would like to use overrided operators from well tested library yet i dont want to learn the rules that make overriding correct. If we always write prog only after careful consideration, then op overriding is not so critical. Sugar is nice. Producing it is exhausting. There is few thing to do with abstraction, OOP grammer in cpp just saves one 'this' pointer that you can pass by yourself, the same as operator overriding. It's about convenience and cost. 【 在 nuanyangyang 的大作中提到: 】 : The point is: making things simpler helps you make less mistakes. I proved this in my project that adding a layer of abstraction not only make your life easier, but also make your program more powerful as well. You will be willing to add features which were way too complicated and you were not brave enough to touch. This is the power of abstraction. :

Just being curious. Are you creating any libraries where operator overriding is helpful? 【 在 qiukun 的大作中提到: 】 : At present, I would like to use overrided operators from well tested library yet i dont want to learn the rules that make overriding correct. If we always write prog only after careful consideration, then op overriding is not so critical. : Sugar is nice. Producing it is exhausting. : There is few thing to do with abstraction, OOP grammer in cpp just saves one 'this' pointer that you can pass by yourself, the same as operator overriding. It's about convenience and cost. : ...................

I have a tiny lib where op overriding is helpful. Most of the codes are pasted. I've mentioned i dont want to learn the rules for op overriding but i'm glad to modify existing codes. 【 在 nuanyangyang 的大作中提到: 】 : Just being curious. Are you creating any libraries where operator overriding is helpful? :

#define REP(i, n) for(int i = 0; i < n; ++i) #define REP(n) REP(i, n) Today i need overriding. Em. Maybe i need lisp's macro? 【 在 nuanyangyang 的大作中提到: 】 : Just being curious. Are you creating any libraries where operator overriding is helpful? :

Why? for(int i=0; i<n; ++i) is the standard C/C++ way of iterating over an array. ... well, unless you intend to unfold the loop. But I believe the compiler can detect this pattern and do it better than you.

No i'm saving typing. 【 在 nuanyangyang 的大作中提到: 】 : Why? for(int i=0; i<n; ++i) is the standard C/C++ way of iterating over an array. : ... well, unless you intend to unfold the loop. But I believe the compiler can detect this pattern and do it better than you.

Then you should really give Ruby a try. C++ is not for saving typing. Your little saving is insignificant comparing to the sheer complexity of C++ itself. 【 在 qiukun 的大作中提到: 】 : No i'm saving typing.