On Mon, 20 Jan 2003 Manish Jethani wrote:
Tahir Hashmi wrote:
On Sat, 18 Jan 2003 19:41:50 +0530 Manish Jethani wrote:
of C/C++'s "unspecified", "undefined" (nasal demons) and "implementation-defined" things have well-defined equivalents in Java.
Use a compiler from just one vendor and use it for just one
Just one vendor?!! Now you've started misguiding people, man!
Do all Java compilers implement the specifications as they are? Don't specifications change with versions? Are all JVMs alike? Of course, I don't program in Java so I won't know but I heard about VJ++ and Microsoft's JVM bundled with WinXP creating some issues. And I also found this: http://pds.twi.tudelft.nl/timber/jacks.html
You're asking people to go back to their GCC/SUNWPro/MSVC++/Borland/blah compiler kit and create relatively unportable/unmaintainable software that ties its users down to one OS.
Yes, because that's what I'd essentially do with Java too. I'd write Java code and it ties users down to a Java Virtual Machine. BTW, I heard about something called "GNU Autotools". They are what enable GNU to provide portability to their software across a wide range of platforms, without much ado. And I won't buy the "unmaintainable" software argument since there's a lot more to maintainability than just a PL.
My point was that they are not exclusive to Java and certainly available in C++.
How about: "No! They're not available in C++."
Eh? Just to remind you:
Garbage Collection: Java (yes, in-built) C++ (yes, through GC libraries) OOP Support: Java (yes, in-built) C++ (yes, in-built and more complete than Java) Dynamic typing: Java (yes, in-built) C++ (yes, in-built, plus in-built static typing too)
PS: Have you, by any chance, read "Thinking in Java"?
Also, I didn't get this message in my mailbox so I had to pick it up from the Archives. This might break threading.