decoration decoration
Stories

GROKLAW
When you want to know more...
decoration
For layout only
Home
Archives
Site Map
Search
About Groklaw
Awards
Legal Research
Timelines
ApplevSamsung
ApplevSamsung p.2
ArchiveExplorer
Autozone
Bilski
Cases
Cast: Lawyers
Comes v. MS
Contracts/Documents
Courts
DRM
Gordon v MS
GPL
Grokdoc
HTML How To
IPI v RH
IV v. Google
Legal Docs
Lodsys
MS Litigations
MSvB&N
News Picks
Novell v. MS
Novell-MS Deal
ODF/OOXML
OOXML Appeals
OraclevGoogle
Patents
ProjectMonterey
Psystar
Quote Database
Red Hat v SCO
Salus Book
SCEA v Hotz
SCO Appeals
SCO Bankruptcy
SCO Financials
SCO Overview
SCO v IBM
SCO v Novell
SCO:Soup2Nuts
SCOsource
Sean Daly
Software Patents
Switch to Linux
Transcripts
Unix Books

Gear

Groklaw Gear

Click here to send an email to the editor of this weblog.


You won't find me on Facebook


Donate

Donate Paypal


No Legal Advice

The information on Groklaw is not intended to constitute legal advice. While Mark is a lawyer and he has asked other lawyers and law students to contribute articles, all of these articles are offered to help educate, not to provide specific legal advice. They are not your lawyers.

Here's Groklaw's comments policy.


What's New

STORIES
No new stories

COMMENTS last 48 hrs
No new comments


Sponsors

Hosting:
hosted by ibiblio

On servers donated to ibiblio by AMD.

Webmaster
java.math.max | 687 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
java.math.max
Authored by: Ed L. on Friday, April 27 2012 @ 02:49 PM EDT
This (operator overloading) is a very useful and powerful technique in object oriented programming.
But not in Java.

:-)

---
Real Programmers mangle their own memory.

[ Reply to This | Parent | # ]

java.math.max
Authored by: kuroshima on Friday, April 27 2012 @ 03:00 PM EDT
Java does not allowing overloaded operators. There is one
overloaded operator in Java, and it's '+', that can be
applied to String objects only (and it's actually a bad
practice to do so, because of the way String objects work*)
to concatenate them. The correct way to handle objects is
with methods. I actually think that not using overloaded
operators leads to cleaner, but more verbose code.


*Strings in Java are strange. Once a String object is
created, it is immutable (it can not be changed), meaning
that to concatenate two String objects, you need to create a
new String object that contains both character strings from
both String objects. Now take a simple program that loops
over a file, reads a line and adds the line to a String
object. If you use +, you end with a memory usage that is
geometric with the number of lines in the file (You don't
explicitly free memory in Java, you let the garbage
collector clean unreferenced objects for you. Helps prevent
memory leaks, but if you don't code well, your program will
stop from time to time while the garbage collector tries to
clear some memory), in that the first line will be read fine
and dandy, then you end up creating a new String that
contains the first line and the second, one that contains
the first, second and third,.... Java has StringBuilder and
StringBuffer to avoid this.
See http://chaoticjava.com/posts/stringbuilder-vs-string/
for a better treatment of this.

[ Reply to This | Parent | # ]

java.math.max
Authored by: Anonymous on Friday, April 27 2012 @ 09:28 PM EDT
Java's implementation of max() is NOT a trivial a>=b?a:b. Besides the
overloading for several types, the float and double versions have extra code to

support NaN and signed zeros (nastiness from IEEE754).

[ Reply to This | Parent | # ]

Groklaw © Copyright 2003-2013 Pamela Jones.
All trademarks and copyrights on this page are owned by their respective owners.
Comments are owned by the individual posters.

PJ's articles are licensed under a Creative Commons License. ( Details )