[909] in java-interest
Re: overloading of operators
daemon@ATHENA.MIT.EDU (Jeremy Fitzhardinge)
Tue Aug 15 01:22:38 1995
From: jeremy@suede.sw.oz.au (Jeremy Fitzhardinge)
To: parrt@parr-research.com (Terence John Parr)
Date: Tue, 15 Aug 1995 12:01:53 +1000 (EST)
Cc: java-interest@java.sun.com
In-Reply-To: <199508142207.PAA02545@lonewolf.parr-research.com> from "Terence John Parr" at Aug 14, 95 03:07:33 pm
> Yeah, count me as a "no way Jose'" on operator overloading. Down
> with C++ where any random stream of ASCII chars is a program. Long live
> the simplicity of Java!!!! I hate C++ because you can never tell what
> you're reading without scanning the entire class hierarchy.
Yes, and a change "way up there" can affect code everywhere. At least
Java doesn't have implicit conversions using class constructors...
> Anybody else wanna "vote" on the 'new' operator and operator overloading?
> Remember silence implies consent!!! If we wait too much longer, Sun
> can claim that too much code exists already to change the language.
You can count me. Cleaner Syntax For A Better Tomorrow.
[Hm. Seems that most implementors don't like the existing syntax
apart from the Sun folk, who've already implemented it...
Must be one of those parser generators vs. hand-written parser
things. I suspect using a hand-written parser does lead one to
do little localized syntax changes without necessarily thinking
about what it does to the overall syntax.]
J
-
Note to Sun employees: this is an EXTERNAL mailing list!
Info: send 'help' to java-interest-request@java.sun.com
