Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

15
  • 7
    If you look at your suggestions you are talking about creating a coding standard. The fact that you are creating and following a standard is actually what is going to increase the maintainability. Commented Jan 25, 2016 at 10:31
  • 65
    Should Java code also be restricted to features, which are also found in C++ language? So don't use for example Java volatile, package-private class member access, reflection/introspection, finally-blocks, checked exceptions, and so on? The whole question kind of doesn't make much sense... C++ and Java are superficially similar, but ultimately very different languages. Commented Jan 25, 2016 at 13:09
  • 5
    How are languages to evolve if people are unwilling to use new features? The purpose of the new features is to make your life easier by solving common problems. If users do not use new features, then there's no motivation for anyone to implement them. Commented Jan 25, 2016 at 14:09
  • 75
    If you want Java, use Java. If you use C++, use C++, not some horrible, twisted imitation of Java with C++ syntax. Using C++ but restricting yourself to Java's feature set gives you the worst of both worlds. Commented Jan 25, 2016 at 17:06
  • 12
    You'd be surprised by how fast the differences will bite you (and hard). SomeObject a = previousObject;does very different things in Java and C++. In Java it copies a reference, while in C++ it copies the object. In Java, modifications to a would also affect the previous object. In C++, you have two separate objects. Commented Jan 26, 2016 at 11:18