Comparison of Java and C++

Language features

Syntax

• Java syntax has a context-free grammar that can be parsed by a simple LALR parser. Parsing C++ is more complicated. For example, Foo<1>(3); is a sequence of comparisons if Foo is a variable, but creates an object if Foo is the name of a class template.
• C++ allows namespace-level constants, variables, and functions. In Java, such entities must belong to some given type, and therefore must be defined inside a type definition, either a class or an interface.
• In Java, all types belong to a namespace (Java package), and there is no such thing as a "global namespace" (even in compact source files where code seemingly does not reside in any class, such code belongs to a final top-level class in the unnamed package), unlike C++ where any code not part of a namespace is part of the global namespace. In Java, the "unnamed package" is not a global namespace, and classes in it cannot be imported by code in named packages.
• Java has a strict global inheritance tree such that all classes (implicitly) extend the top type, java.lang.Object. C++ does not have any global inheritance tree. It does have a top type std::any, but is a type-erased runtime object rather than an inherited type.
• In C++, objects are values, while in Java they are not. C++ uses value semantics by default, while Java always uses reference semantics. To opt for reference semantics in C++, either a pointer or a reference can be used.

• C++ supports goto statements, which may lead to spaghetti code programming. With the exception of the goto statement (which is very rarely seen in real code and highly discouraged), both Java and C++ have basically the same control flow structures, designed to enforce structured control flow, and relies on break and continue statements to provide some goto-like functions. Some commenters point out that these labelled flow control statements break the single point-of-exit property of structured programming.
• C++ provides low-level features which Java mostly lacks (one notable exception being the internal sun.misc.Unsafe API for direct memory access and manipulation). In C++, pointers can be used to manipulate specific memory locations, a task necessary for writing low-level operating system components. Similarly, many C++ compilers support an inline assembler, and assembly functions may be linked in C/C++ programs. In Java, such code must reside in external libraries, and can only be accessed via the Java Native Interface, with a significant overhead for each call.

Semantics

• C++ allows default values for arguments of a function/method. Java does not. However, method overloading can be used to obtain similar results in Java but generate redundant stub code.
• The minimum of code needed to compile for C++ is a function, for Java is a class. However, since Java 21 with the introduction of the unnamed class, it is possible to write a Java program consisting only of a main function.
• C++ allows a range of implicit conversions between native types (including some narrowing conversions), and also allows defining implicit conversions involving user-defined types. In Java, only widening conversions between native types are implicit; other conversions require explicit cast syntax.
  • A result of this is that although loop conditions (if, while and the exit condition in for) in Java and C++ both expect a Boolean expression, code such as if (a = 5) will cause a compile error in Java because there is no implicit narrowing conversion from int to Boolean, but will compile in C++. This is handy if the code was a typo and if (a == 5) was intended. However, current C++ compilers will usually generate a warning when such an assignment is performed within a conditional expression. Similarly, standalone comparison statements, e.g. a == 5;, without a side effect usually lead to a warning.
• For passing parameters to functions, C++ supports both pass-by-reference and pass-by-value. In Java, primitive parameters are always passed by value. Class types, interface types, and array types are collectively called reference types in Java and are also always passed by value.
• Java built-in types are of a specified size and range defined by the language specification. In C++, a minimal range of values is defined for built-in types, but the exact representation (number of bits) can be mapped to whatever native types are preferred on a given platform.
  • For instance, Java characters are 16-bit Unicode characters, and strings are composed of a sequence of such characters. C++ offers both narrow and wide characters, but the actual size of each is platform dependent, as is the character set used. Strings can be formed from either type.
  • This also implies that C++ compilers can automatically select the most efficient representation for the target platform (i.e., 64-bit integers for a 64-bit platform), while the representation is fixed in Java, meaning the values can either be stored in the less-efficient size, or must pad the remaining bits and add code to emulate the reduced-width behavior.
• The rounding and precision of floating point values and operations in C++ is implementation-defined (although only very exotic or old platforms depart from the IEEE 754 standard). Java provides an optional strict floating-point model (strictfp) that guarantees more consistent results across platforms, though at the cost of possibly slower run-time performance. However, Java does not comply strictly with the IEEE 754 standard. Most C++ compilers will, by default, comply partly with IEEE 754 (usually excluding strict rounding rules and raise exceptions on NaN results), but provide compliance options of varied strictness, to allow for some optimizing. If we label those options from least compliant to most compliant as fast, consistent (Java's strictfp), near-IEEE, and strict-IEEE, we can say that most C++ implementations default to near-IEEE, with options to switch to fast or strict-IEEE, while Java defaults to fast with an option to switch to consistent.
• In C++, pointers can be manipulated directly as memory address values. Java references are pointers to objects. Java references do not allow direct access to memory addresses or allow memory addresses to be manipulated with pointer arithmetic. In C++ one can construct pointers to pointers, pointers to ints and doubles, and pointers to arbitrary memory locations. Java references only access objects, never primitives, other references, or arbitrary memory locations. In Java, memory can be read and written by arbitrary values using the sun.misc.Unsafe API, however it is deprecated and not recommended.
• In C++, pointers can point to functions or member functions (function pointers). The equivalent mechanism in Java uses object or interface references.
• Via stack-allocated objects, C++ supports scoped resource management, a technique used to automatically manage memory and other system resources that supports deterministic object destruction. While scoped resource management in C++ cannot be guaranteed (even objects with proper destructors can be allocated using new and left undeleted) it provides an effective means of resource management. Shared resources can be managed using std::shared_ptr<T>, along with std::weak_ptr<T> to break cyclic references. Java supports automatic memory management using garbage collection which can free unreachable objects even in the presence of cyclic references, but other system resources (files, streams, windows, communication ports, threads, etc.) must be explicitly released because garbage collection is not guaranteed to occur immediately after the last object reference is abandoned. Java allows scope resource management through try-with-resources blocks for types that implement java.lang.AutoCloseable, but unlike C++, the object is not disposed from memory, but only owned resources are disposed by the close() method.
• C++ features user-defined operator overloading. Operator overloading allows for user-defined types to support operators (arithmetic, comparisons, etc.) like primitive types via user-defined implementations for these operators. It is generally recommended to preserve the semantics of the operators. Java supports no form of operator overloading (although its library uses the addition operator for string concatenation).
• Java features standard application programming interface (API) support for reflective programming (reflection) and dynamic loading of arbitrary new code.
• C++ supports static and dynamic linking of binaries.
• Both Java and C++ (since C++26) offer reflection, allowing for a degree of code introspection. Reflection in Java acts primarily at runtime and is primarily behavioral, while reflection in C++ acts at compile-time and produces meta-objects, and is primarily generative.
• Java has generics, which main purpose is to provide type-safe containers. However, Java generics are not reified (act only at compile-time), and are type-erased at runtime. C++ has compile-time templates, which provide more extensive support for generic programming and metaprogramming. C++ templates instantiate a specialization for each type used with them.
• Both Java and C++ offer annotations. Java annotations allow adding arbitrary custom metadata to classes and metaprogramming via an annotation processing tool. C++ offers attributes to indicate compiler-defined metadata, as well as annotations (since C++26) which can user-defined and read at compile time, but not at runtime like in Java.
• Both Java and C++ distinguish between native types (also termed fundamental or built-in types) and user-defined types (also termed compound types). In Java, native types have value semantics only, and compound types have reference semantics only. In C++ all types have value semantics, but a reference can be created to any type, which will allow the object to be manipulated via reference semantics.
• C++ supports multiple inheritance of arbitrary classes. In Java a class can derive from only one class, but a class can implement multiple interfaces (in other words, it supports multiple inheritance of types, but only single inheritance of implementation).
• Java explicitly distinguishes between interfaces and classes. In C++, multiple inheritance and pure virtual functions make it possible to define classes that function almost like Java interfaces do, with a few small differences.
• Java has both language and standard library support for multi-threading. The synchronized keyword in Java provides mutex locks to support multi-threaded applications. Java also provides libraries for more advanced multi-threading synchronizing. C++11 has a defined memory model for multi-threading in C++, and library support for creating threads and for many synchronizing primitives.
• C++ member functions can be declared as virtual functions, which means the method to be called is determined by the run-time type of the object (a.k.a. dynamic dispatching). By default, methods in C++ are not virtual (i.e., opt-in virtual). In Java, methods are virtual by default, but can be made non-virtual by using the final keyword (i.e., opt-out virtual).
• C++ features a language-level override keyword to indicate overriding a virtual method. Java does not, but features a @Override annotation to indicate overriding, which issues a compiler error if no existing method is being overriden.
• C and C++ enumerations are primitive types. C enumerations (enum) implicitly convert to integer types (but not from integer types), while C++ enumerations (enum class) are strongly typed and do not implicitly convert. Java enumerations behave like classes and may define constructors and methods.
• Unary operators ++ and --: in C++ "The operand shall be a modifiable lvalue. [skipped] The result is the updated operand; it is an lvalue...", but in Java "the binary numeric promotion mentioned above may include unboxing conversion and value set conversion. If necessary, value set conversion {and/or [...] boxing conversion} is applied to the sum prior to its being stored in the variable.", i.e. in Java, after the initialization Integer i = 2; ++i; changes the reference i by assigning new object, while in C++ the object is still the same.
• In Java, lambdas are "poly expressions", whose types dependent on context, while in C++, lambdas have a real runtime class which can be accessed with decltype and are part of the language model. Java lambdas depend on the functional interface which they are assigned to.

Resource management

• Java offers automatic garbage collection, which may be bypassed in specific circumstances via the Real time Java specification. Memory management in C++ is usually done via constructors, destructors, and smart pointers. The C++ standard permits garbage collection, but does not require it. Garbage collection is rarely used in practice.
• C++ can allocate arbitrary blocks of memory. Java only allocates memory via object instantiation. Arbitrary memory blocks may be allocated in Java as an array of bytes.
• Java and C++ use different idioms for resource management. Java relies mainly on garbage collection, which can reclaim memory, while C++ relies mainly on the Resource Acquisition Is Initialization (RAII) idiom. This is reflected in several differences between the two languages:
  • In C++ it is common to allocate objects of compound types as local stack-bound variables which are destroyed when they go out of scope. In Java compound types are always allocated on the heap and collected by the garbage collector (except in virtual machines that use escape analysis to convert heap allocations to stack allocations).
  • C++ has destructors, while Java has finalizers. Both are invoked before an object's deallocation, but they differ significantly. A C++ object's destructor must be invoked implicitly (in the case of stack-bound variables) or explicitly to deallocate an object. The destructor executes synchronously just before the point in a program at which an object is deallocated. Synchronous, coordinated uninitializing and deallocating in C++ thus satisfy the RAII idiom. Destructors in C++ is the normal way of getting back the resources associated with an object, and is a needed counterpart to constructors. In Java, object deallocation is implicitly handled by the garbage collector. A Java object's finalizer is invoked asynchronously some time after it has been accessed for the last time and before it is deallocated. Very few objects need finalizers. A finalizer is needed by only objects that must guarantee some cleanup of the object state before deallocating, typically releasing resources external to the JVM. Direct usages of finalizers are usually not advised, as they are unpredictable, usually dangerous, and most of the time unneeded. One has to be cautious not to think of finalizers as C++ destructors. Rather, the try-with-resources or try-finally block achieves a more similar purpose as the destructor. One problem with finalizers or cleaners is that it is not guaranteed that they will run immediately. Hence, a finalizer should never be used for tasks that are time-critical. Additionally, finalizers come with severe performance penalties and significantly increase the time it takes for objects to be deallocated, so their use is discouraged and deprecated in Java 9.
  • With RAII in C++, one type of resource is typically wrapped inside a small class that allocates the resource upon construction and releases the resource upon destruction, and provide access to the resource in between those points. Any class that contain only such RAII objects do not need to define a destructor since the destructors of the RAII objects are called automatically as an object of this class is destroyed. In Java, safe synchronous deallocation of resources can be performed deterministically using the try-catch-finally construct. Alternatively, the try-with-resources construct, which was introduced in Java 7, should be used in preference to try-finally construct. The try-with-resources construct is more concise and readable. It also provide more helpful diagnostic information, since suppressed exception are not discarded, and will be printed in the stack trace with information saying that they were suppressed.
  • In C++, it is possible to have a dangling pointer, a stale reference to an object that has already been deallocated. Attempting to use a dangling pointer typically results in program failure. In Java, the garbage collector will not destroy a referenced object.
  • In C++, it is possible to have uninitialized primitive objects. Java enforces default initialization.
  • In C++, it is possible to have an allocated object to which there is no valid reference. Such an unreachable object cannot be destroyed (deallocated), and results in a memory leak. In contrast, in Java an object will not be deallocated by the garbage collector until it becomes unreachable (by the user program). (Weak references are supported, which work with the Java garbage collector to allow for different strengths of reachability.) Garbage collection in Java prevents many memory leaks, but leaks are still possible under some circumstances. The automatic garbage collector may give the false impression that in Java one does not need to think about memory management. However this is not quite true. Loosely speaking, this is because a program can have "memory leaks", more formally known as "unintentional object retentions". An example of a memory leak that may occur is for a program that has been written without any logical errors, except that it did not eliminate obsolete references. This results in higher use of garbage collector activity, higher memory footprint. In extreme circumstances, this problem can lead to an java.lang.OutOfMemoryError, but this rarely happens.

The solution to this is to null out object references. A second common reason for memory leak is the use of cache that has become no longer relevant. The solution to memory leaks due to using old cache is to represent the cache using a java.util.WeakHashMap<K, V>.

Libraries

• C++ provides cross-platform access to many features typically available in platform-specific libraries. Direct access from Java to native operating system and hardware functions requires the use of the Java Native Interface, or since Java 21, the Foreign Function and Memory API, which allow for allocating and managing memory outside of the Java Virtual Machine, as well as calling native (i.e. C/C++) functions.
• The C++ standard library is designed to be minimalistic, providing only a standardised set of general use features, while the Java Class Library and Java Platform Module System (the Java standard library) is much more extensive, providing a much larger comprehensive standardised set of features, such as graphics, UI creation, and more.

Runtime

• Due to its unconstrained expressiveness, low level C++ language features (e.g. unchecked array access, raw pointers, type punning) cannot be reliably checked at compile-time or without overhead at run-time. Related programming errors can lead to low-level buffer overflows and segmentation faults. The Standard Template Library provides higher-level RAII abstractions (like vector, list and map) to help avoid such errors. In Java, low level errors either cannot occur or are detected by the Java virtual machine (JVM) and reported to the application in the form of an exception.
  • Exceptions are tightly coupled in the Java runtime and language-level operations (including but not limited to division-by-zero, null reference access, invalid casting, and out-of-bounds array access) may throw exceptions, whereas in C++ typically only objects throw (with the exception of the typeid() which may throw a std::bad_typeid exception, new which may throw std::bad_alloc or std::bad_array_new_length, new which may throw std::bad_alloc, or dynamic_cast which may throw std::bad_cast). Furthermore, in C++, exceptions may be "disabled" (such as with -no-exceptions on GCC or Clang, or /Ehsc on MSVC), which will prevent the compiler from generating code for exception handling, and terminate a program with std::terminate() upon a throw statement.
  • Java features checked exceptions, which are exceptions that must be handled in a catch block, and can only be allowed to propagate through functions that explicitly declare them with a throws clause. Any exception which does not extend java.lang.RuntimeException is considered a checked exception. Meanwhile, in C++, the concept of "checked exceptions" does not exist, but functions may be specified not to throw with a noexcept specifier. Until C++17, C++ allowed dynamic exception specifications through a throw clause in the function signature, which like Java throws clauses, allowed functions to specify which types may be thrown.
  • Java allows only classes which extend java.lang.Throwable to be thrown by a throw statement. In C++, any object, including primitives, may be thrown and caught. Java differentiates between java.lang.Error (representing runtime errors considered unreasonable to catch) and java.lang.Exception (representing possible recoverable errors considered reasonable to catch) while in C++, the usual base exception class is std::exception.
• The Java language requires specific behavior in the case of an out-of-bounds array access, which generally requires bounds checking of array accesses. This eliminates a possible source of instability but usually at the cost of slowing execution. In some cases, especially since Java 7, compiler analysis can prove a bounds check unneeded and eliminate it. C++ has no required behavior for out-of-bounds access of native arrays, thus requiring no bounds checking for native arrays. C++ standard library collections like std::vector<T>, however, offer optional bounds checking. In summary, Java arrays (T[]) are "usually safe; slightly constrained; often have overhead" while C++ native arrays "have optional overhead; are slightly unconstrained; are possibly unsafe." Java collections like java.util.ArrayList<T> can throw exceptions like java.lang.IndexOutOfBoundsException. C++26 adds "bounds hardening" to the standard library, which now define certain undefined behaviors (including out-of-bounds access) to be contract violations.

Templates vs. generics

Both C++ and Java provide facilities for generic programming, templates and generics, respectively. Although they were created to solve similar kinds of problems, and have similar syntax, they are quite different.

Asynchronous/concurrent programming

• Java lacks an asynchronous runtime entirely. Java traditionally relies on thread pools managed by a java.util.concurrent.ExecutorService, which runs on an operating system multi-threading. For non-blocking I/O, Java offers java.nio.
• Java 21 with Project Panama introduces virtual threads (similar to Go's "goroutines" which are analogous to green threads), allowing writing traditional blocking code inside a virtual thread with automatic unmounting and remounting.
• C++20 introduces true coroutines, C++23 introduces generators in the standard library, and C++26 introduces an asynchronous task type in the standard library. C++20 introduces three new keywords (but no async keyword):
  • co_await: suspends execution until resumed, analogous to await in other languages
  • co_yield: suspends execution, returning a value, analogous to yield in other languages' generators
  • co_return: completes execution, returning a value
• C++26 introduces the std::execution library, which is a lazy, composable, zero-overhead framework, while Java's java.util.concurrent.ExecutorService is an eager runtime. Java yields the execution control to the internal task queue, while C++ only starts execution when a receiver connects to a sender and calls start().
  • C++'s std::execution::scheduler is an execution engine, analogous to Java's java.util.concurrent.ExecutorService.
  • C++'s std::execution::sender is an async pipeline, analogous to Java's java.util.concurrent.CompletableFuture<T>.
  • C++'s std::execution::receiver is a callback/sink, analogous to Java's internal completion handlers/lambdas.
  • Java lacks a true equivalent to C++'s std::execution::task<T, Env>, which represents a unit of asynchronous work, and is a sender that is often used as a coroutine's return type to be co_awaited.
• Older C++ used std::async() (introduced in C++11), which receives a unit of work (a lambda) and returns a std::future<T> as a receipt, similar to Java's ExecutorService.submit() which returned a java.util.concurrent.Future<T>.

Miscellaneous

• Java and C++ use different means to divide code into multiple source files.
  • Java uses a package system that dictates the file name and path for all program definitions. Its compiler imports the executable class files.
  • Prior to C++20, C++ used a header file source code inclusion system to share declarations between source files. Since C++20, however, modules were introduced offering similar functionality to Java packages. All symbols marked export are accessible after importing a module.
  • Since C++23, the C++ standard library can now be imported as a module.
• The term "module" refers to different things. In Java, a module is used to group several packages together, meanwhile in C++ a module represents a single translation unit that is declared as a module.
  • import in C++ imports a module by loading its BMI (built module interface) at compilation, however in C++, modules do not dictate the namespace which a symbol belongs to. Meanwhile, import in Java is used to alias classes to avoid fully qualifying them (equivalent to using in C++), and does not "import" definitions during compiilation. This is because all classes are handled as needed during runtime by the Java class loader on demand, and can be used even without an import statement by fully qualifying the class.
• A Java source file must match the namespace which of the public class it declares (it may be named anything if there are no public classes), and the package it belongs to must match the path it is located in. A package may only declare at most one public class (but may have multiple non-public classes).
• A C++ source file (whether a header or module) may have any arbitrary name, and may contain as many classes as the programmer desires. Modules have no requirement to match the path of its location.
• Compiled Java class files are generally smaller than object files in C++ as Java bytecode is usually more compact than native machine code, and Java does not perform static linking.
• C++ compiling features an added textual preprocessing phase, while Java does not. Thus some users add a preprocessing phase to their build process for better support of conditional compiling.
• Java's division and modulus operators are well defined to truncate to zero. Prior to C++11, C++ did not specify whether or not these operators truncate to zero or "truncate to negative infinity". -3/2 will always be -1 in Java and C++11, but a C++03 compiler may return either -1 or -2, depending on the platform. C99 defines division in the same fashion as Java and C++11. Both languages guarantee (where a and b are integer types) that (a / b) * b + (a % b) == a for all a and b (b non-zero). The C++03 version will sometimes be faster, as it is allowed to pick whichever truncation mode is native to the processor.
• The sizes of integer types are fixed in Java (for example int is 32-bit, long is 64-bit), while in C++ the size of integers and pointers is compiler and application binary interface (ABI) dependent within given constraints. Thus a Java program will have consistent behavior across platforms, whereas a C++ program may require adapting for some platforms, but may run faster with more natural integer sizes for the local platform. However, C/C++ also have fixed width sizes (such as int32_t for signed 32-bit integers, uint64_t for unsigned 64-bit integers, etc.)

An example comparing C++ and Java exists in Wikibooks.

Performance

In addition to running a compiled Java program, computers running Java applications generally must also run the Java virtual machine (JVM), while compiled C++ programs can be run without external applications. Early versions of Java were significantly outperformed by statically compiled languages such as C++. This is because the program statements of these two closely related languages may compile to a few machine instructions with C++, while compiling into several byte codes involving several machine instructions each when interpreted by a JVM. For example:

Since performance optimization is a very complex issue, it is very difficult to quantify the performance difference between C++ and Java in general terms, and most benchmarks are unreliable and biased. Given the very different natures of the languages, definitive qualitative differences are also difficult to draw. In a nutshell, there are inherent inefficiencies and hard limits on optimizing in Java, given that it heavily relies on flexible high-level abstractions, however, the use of a powerful JIT compiler (as in modern JVM implementations) can mitigate some issues. In any case, if the inefficiencies of Java are too great, compiled C or C++ code can be called from Java via the JNI.

Some inefficiencies that are inherent to the Java language include, mainly:

• All objects are allocated on the heap. Though allocation is extremely fast in modern JVMs using 'bump allocation', which performs similarly to stack allocation, performance can still be negatively impacted due to the invocation of the garbage collector. Modern JIT compilers mitigate this problem to some extent with escape analysis or escape detection to allocate some objects on the stack, since Oracle JDK 6.
• Performance-critical projects like efficient database systems and messaging libraries have had to use internal unofficial APIs like sun.misc.Unsafe to gain access to manual resource management and be able to do stack allocation; effectively manipulating pseudo-pointers.
• A lot of run-time casting required even using standard containers induces a performance penalty. However, most of these casts are statically eliminated by the JIT compiler.
• Safety guarantees come at a run-time cost. For example, the compiler is required to put appropriate range checks in the code. Guarding each array access with a range check is not efficient, so most JIT compilers will try to eliminate them statically or by moving them out of inner loops (although most native compilers for C++ will do the same when range-checks are optionally used).
• Lack of access to low-level details prevents the developer from improving the program where the compiler is unable to do so.
• The mandatory use of reference-semantics for all user-defined types in Java can introduce large amounts of superfluous memory indirections (or jumps) (unless elided by the JIT compiler) which can lead to frequent cache misses (a.k.a. cache thrashing). Furthermore, cache-optimization, usually via cache-aware or cache-oblivious data structures and algorithms, can often lead to orders of magnitude improvements in performance as well as avoiding time-complexity degeneracy that is characteristic of many cache-pessimizing algorithms, and is therefore one of the most important forms of optimization; reference-semantics, as mandated in Java, makes such optimizations impossible to realize in practice (by neither the programmer nor the JIT compiler).
• Garbage collection, as this form of automatic memory management introduces memory overhead.

However, there are a number of benefits to Java's design, some realized, some only theorized:

• Java garbage collection may have better cache coherence than the usual use of std::malloc/new for memory allocation. Nevertheless, arguments exist that both allocators equally fragment the heap and neither exhibits better cache locality. However, in C++, allocation of single objects on the heap is rare, and large quantities of single objects are usually allocated in blocks via an STL container and/or with a small object allocator.
• Run-time compiling can potentially use information about the platform on which the code is being executed to improve code more effectively. However, most state-of-the-art native (C, C++, etc.) compilers generate multiple code paths to employ the full computational abilities of the given system. Also, the inverse argument can be made that native compilers can better exploit architecture-specific optimizing and instruction sets than multi-platform JVM distributions.
• Run-time compiling allows for more aggressive virtual function inlining than is possible for a static compiler, because the JIT compiler has more information about all possible targets of virtual calls, even if they are in different dynamically loaded modules. Currently available JVM implementations have no problem in inlining most of the monomorphic, mostly monomorphic and dimorphic calls, and research is in progress to inline also megamorphic calls, thanks to the recent invoke dynamic enhancements added in Java 7. Inlining can allow for further optimisations like loop vectorisation or loop unrolling, resulting in a huge overall performance increase.
• In Java, thread synchronizing is built into the language, so the JIT compiler can potentially, via escape analysis, elide locks, significantly improve the performance of naive multi-threaded code.

Also, some performance problems occur in C++:

• Allowing pointers to point to any address can make optimizing difficult due to the possibility of pointer aliasing.
• Since the code generated from various instantiations of the same class template in C++ is not shared (as with type-erased generics in Java), excessive use of templates may lead to significant increase of the executable code size (code bloat). However, because function templates are aggressively inlined, they can sometimes reduce code size, but more importantly allow for more aggressive static analysis and code optimizing by the compiler, more often making them more efficient than non-templated code. In contrast, Java generics are necessarily less efficient than non-genericized code.
• Because in a traditional C++ compiler, dynamic linking is performed after code generating and optimizing in C++, function calls spanning different dynamic modules cannot be inlined. However modern C++ compilers like MSVC and Clang+LLVM offer link-time-code-generation options that allow modules to be compiled to intermediate formats which allows inlining at the final link stage.

Official standard and reference of the language

Language specification

The C++ language is defined by ISO/IEC 14882, an ISO standard, which is published by the ISO/IEC JTC1/SC22/WG21 committee. C++ typically releases on a three-year cycle.

The C++ language evolves via an open steering committee called the C++ Standards Committee. The committee is composed of the creator of C++ Bjarne Stroustrup, the convener Herb Sutter, and other prominent figures, including many representatives of industries and user-groups (i.e., the stake-holders). Being an open committee, anyone is free to join, participate, and contribute proposals for upcoming releases of the standard and technical specifications. The committee now aims to release a new standard every few years, although in the past strict review processes and discussions have meant longer delays between publication of new standards (1998, 2003, and 2011).

The Java language is defined by the Java Language Specification, a book which is published by Oracle. Java typically releases on a semiannual cycle, though traditionally released once every two years.

The Java language continuously evolves via a process called the Java Community Process, and the world's programming community is represented by a group of people and organizations - the Java Community members—which is actively engaged into the enhancement of the language, by sending public requests - the Java Specification Requests - which must pass formal and public reviews before they get integrated into the language.

The lack of a firm standard for Java and the somewhat more volatile nature of its specifications have been a constant source of criticism by stake-holders wanting more stability and conservatism in the addition of new language and library features. In contrast, the C++ committee also receives constant criticism, for the opposite reason, i.e., being too strict and conservative, and taking too long to release new versions.

Trademarks

"C++" is not a trademark of any company or organization and is not owned by any individual. "Java" is a trademark of Oracle.