[527] in java-interest
Re: Operator overloading
daemon@ATHENA.MIT.EDU (Wayne Pinette)
Wed Jun 28 13:58:55 1995
Date: Wed, 28 Jun 95 10:33:51 PDT
From: pinette@mprgate.mpr.ca (Wayne Pinette)
To: java-interest@java.sun.com
If I may stick my two cents worth (which according to some is
all it's worth :-)
I will agree that operator overloading can be a big bug infested
pain in the lower posterior. Especially when I am hired to maintain
a piece of hacked together code written by a co-op student (I wish
some of you could look at my other window right now :-). But let's
all be honest here. operator overloading is very powerful and very
handy in certain occasions. With that power comes control. If a
programmer has no control, then they are going to write sloppy code
whether you give them operator overloading or not. They will still
find a way to screw things up. I think it is up to the programmer
to decide whether an object needs an overloaded operator or a function,
not the creator of the compiler. So really, there is not can of worms
to open. It would be nice if Java had operator overloading. I myself
would not use it all the time (the matrix problem Mr. mlorton@eshop.com
would be an example) but there are most certainly cases (object iterators
for example) where I would use it. Think of it this way.... chunky soup,
eat it with a fork or a spoon....the makers of chunky leave it up to the
user. :-)
hmmmm that analogy seems kinda wierd...oh well :-)
Wayner
-------------------------------------------------------------------------------
Wayne Pinette, pinette@mprgate.mpr.ca
/ \ http://jester.mpr.ca:8000/people/wayner/wayner.html
|
\___/ aka Wayner, Gandolf the 23rd (long story :-)
-------------------------------------------------------------------------------
-
Note to Sun employees: this is an EXTERNAL mailing list!
Info: send 'help' to java-interest-request@java.sun.com
