Forums
New posts
Search forums
Members
Current visitors
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Menu
Log in
Register
Install the app
Install
Forums
Archive
Archive
Java
operator overloading
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
[QUOTE="Leonard Milcin, post: 3522164"] Well. It really depends what do you mean by ,,better''. I consider the lack of operator overloading an advantage because it helps to understand the code. Also, operator overloading is frequently abused making it very difficult to analyze the code. It is not only about reading the code. Think of all the great tools like IntelliJ IDEA. They exist only because Java is quite easy to analyze statically. While operator overloading would not prevent static analysis it would certainly make it harder. Think that it will make cost of creating good tools higher which means less tools for higher price. Think of all the people that have to learn Java. With time, Java Language Specification gets longer and longer as it incorporates more and more features. While it may be easy for you to learn new features for the new release, people starting with Java have to learn it all which gets increasingly harder. In mine opninion things like closures only pollute language while not helping anything that couldn't be addressed without them. Then think that when anything is included into Java we're stuck with it FOR LIFE or until we change the language for something different. Isn't it much for changing Time t3 = Time.add(t, t2); to Time t3 = t + t2; ? Best regards, Leonard [/QUOTE]
Verification
Post reply
Forums
Archive
Archive
Java
operator overloading
Top