At what point will Java become a different language? Maybe Tea? What I mean is, adding to the API is one thing, but when you add grammer and syntax it seems that you are actually changing, albeit improving, the language. But then is it still the same langauge? At what point might Java change so much it ceases to be what we know as the Java language?
Or will Sun just continue to increase the version number?
Well, C++ has gone through some pretty incredible changes over the years; from the original "C with Classes" to CFront, C++ was seen as a practical version of extreme O-O languages like Eiffel and Smalltalk. It was all about inheritance then. The language hit a terrible quagmire as people found flaw after flaw in the dark corners of the concept of multiple (especially virtual) inheritance in C++.
Then exceptions were introduced. Scary. Took years for the concept of "exception safety" to be figured out. Utterly changed how people wrote code in C++.
And namespaces. And Koenig lookup. And an utterly new, practically unrecogniable standard library -- along with new names for all the standard header files.
And templates! Now it's barely about inheritance at all anymore; now it's all about generic programming, and, if you're lucky and have a fun job, it's all about metaprogramming -- i.e., to what extent can you make the compiler do all the work so that nothing actually happens at runtime!
But ever since the first public release from AT&T, it's been called "C++".
Originally posted by Gregg Bolinger: At what point will Java become a different language? Maybe Tea? What I mean is, adding to the API is one thing, but when you add grammer and syntax it seems that you are actually changing, albeit improving, the language. But then is it still the same langauge? At what point might Java change so much it ceases to be what we know as the Java language?
I think the key difference is that they are improving the language by adding new functionality, e.g. generics. I see that like frosting on a cake - it just makes it taste better, but it's still a cake.
Blake Minghelli<br />SCWCD<br /> <br />"I'd put a quote here but I'm a non-conformist"
Java will probably always be known as Java until the next hot language is widely accepted. The definition of Java is another thing. The language will always expand to handle new technologies and market demands. Without ongoing changes there probably would have been a replacement language already.
As long as the new version is built on top of the old properties of Java, I think Java will still be called as Java. But who knows? One day there might be a big change as C to C++ like Mr.Ernest mentioned above and Java might be changed to Java** or something. but I do hope that this could be happened only after a new organization tried to invent a new language which is extremely similar to Java...
But for now, Java is still Java. But I think the name "Java 1.5" makes more sense than Java 5.
Co-author of SCMAD Exam Guide, Author of JMADPlus SCJP1.2, CCNA, SCWCD1.4, SCBCD1.3, SCMAD1.0, SCJA1.0, SCJP6.0
Igor, was it not because of PL/1 and Algol68 that the quest for less complex languages like B and C started? Oh I forgot Pascal was a simplification too. [ June 30, 2004: Message edited by: Barry Gaunt ]