开发者

Java cannot overload any operators. Why? [duplicate]

开发者 https://www.devze.com 2022-12-27 05:28 出处:网络
This question already has answers here: Closed 12 years ago. Possible Duplicate: Java operator overload In c++, we can perform the oper开发者_JAVA技巧ator overloading. But Java is also a
This question already has answers here: Closed 12 years ago.

Possible Duplicate:

Java operator overload

In c++, we can perform the oper开发者_JAVA技巧ator overloading. But Java is also a Object oriented language. So why java doesn't support overloading?


http://java.sun.com/docs/white/langenv/Simple.doc2.html

There are no means provided by which programmers can overload the standard arithmetic operators. Once again, the effects of operator overloading can be just as easily achieved by declaring a class, appropriate instance variables, and appropriate methods to manipulate those variables. Eliminating operator overloading leads to great simplification of code.

The last statement is of course very subjective.


Actually, it does support operator overloading... of a very limited, built-in only nature. For instance "+" is overloaded for String's in addition to the usual arithmetic.

Of course, most people want to know why Java does not support user-defined operator overloading. :-) The simplest answer seems to be that the Java creators did not, at the time, see any clean way to add it to the language without making Java a mess (like C++) in the process.


it's design goals to make java simpler than c++

We wanted to build a system that could be programmed easily without a lot of esoteric training and which leveraged today’s standard practice. So even though we found that C++ was unsuitable, we designed Java as closely to C++ as possible in order to make the system more comprehensible. Java omits many rarely used, poorly understood, confusing features of C++ that, in our experience, bring more grief than benefit.

from here: The Java Language: An Overview


The code is harder to understand when you use operator overloading in c++. May be that was the reason why Java developers decided not to implement it. Really the code rich with overloaded operators can be very misleading and hard to read, just like the code with a plenty of macros.


Note that there's an anomaly in that the 'plus' operator is overloaded for java.lang.String.


Way back when, the news was that the Java team looked at other languages (primarily C++) and tried to make a judgment call as to what language level features to include (or exclude) from Java.

Operator overloading was a big new feature in C++ and lots of budding programmers used it to solve problems in interesting ways. Unfortunately, most of those ways were buggy, and few programmers overloaded operators in ways that were "programmer portable". As a result, reading a program would often miss that "magic" code had been introduced in the "+" operator (or something else). Outside of numbers (vectors, etc.) you also had disagreements as to what "+" might mean.

So the cover story (no idea if it was true) was that the Java team saw that you could just name methods sum.plus(...) and it would be obvious that the call was to user written code (which could be overloaded) while the reserved operations "+", etc. would only did what the language defined. This would increase some types of code readability at the expense of a few extra words.

Is it true, or is it an attempt to back fill history with rationalizations? I don't know. Perhaps the language implementers just were busy trying to get Java working and didn't get around to operator overloading by release date. Either way, it greatly increases the readability of Java in 95% of all cases, at the expense of making vector math a bit wordy.

0

精彩评论

暂无评论...
验证码 换一张
取 消