Content deleted Content added
→Some missing points: new section |
→Some missing points: add one benefit of C++ being unsafe |
||
Line 641:
I think there are a few points that are either glossed over or not discussed thoroughly enough in this article. Here's a list of what I think could be covered better:
* Java is a typesafe language. Many errors that can happen in C++ are either disallowed by Java's bytecode verifier or trapped at runtime. [[Buffer overflow]] problems are just one example. On the other hand, this can allow C++ to have better performance ([http://blog.llvm.org/2011/05/what-every-c-programmer-should-know_21.html reference]).
* Java does not have the [[fragile binary interface problem]] problem that C++ does. This is glossed over by the general term "binary compatibility", but the article doesn't seem to explain the repercussions of binary compatibility or the lack of it.
* Java does not have separate [[header files]] as C++ does. This could be consider a strength or weakness, but some advantages are that makefile dependencies do not need to be updated in Java, and Javadoc comments allow documentation for classes and interfaces separate from the source code.
| |||