Criticism of C++

C++ is a general-purpose programming language with imperative, object-oriented, and generic programming features. Many criticisms have been leveled at C++'s design by well-known software developers including Linus Torvalds, Richard Stallman, Joshua Bloch, Rob Pike, Ken Thompson, and Donald Knuth.

C++ is a multi-paradigm programming language with extensive, but not complete, backward compatibility with C. This article focuses not on C features like pointer arithmetic, operator precedence or preprocessor macros, but on pure C++ features that are often criticized.

Slow compile times

The natural interface between source files in C/C++ are header files. Each time a header file is modified, all source files that include the header file should recompile their code. Header files are slow because they are textual and context-dependent as a consequence of the preprocessor. C only has limited amounts of information in header files, the most important being struct declarations and function prototypes. C++ stores its classes in header files and they not only expose their public variables and public functions (like C with its structs and function prototypes) but also their private functions. This forces unnecessary recompiles of all source files that include the header file, each time when changing these private functions. This problem is magnified where the classes are written as templates, forcing all of their code into the slow header files, which is the case with the whole C++ standard library. Large C++ projects can therefore be relatively slow to compile. The problem is largely solved by precompiled headers in modern compilers.

One suggested solution is to use a module system. A module library is planned to be released in C++20, with future C++ releases planning to expose the functionality of the standard library using modules.

Global format state of <iostream>

C++ <iostream> unlike C <stdio.h> relies on a global format state. This fits very poorly together with exceptions, when a function must interrupt the control flow, after an error, but before resetting the global format state. One fix for this is to use Resource Acquisition Is Initialization (RAII) which is implemented in Boost but is not a part of the C++ Standard Library.

The global state of <iostream> uses static constructors which causes overhead. Another source of bad performance is the use of std::endl instead of '\n' when doing output, because of it calling flush as a side effect. C++ <iostream> is by default synchronized with <stdio.h> which can cause performance problems. Shutting it off can improve performance but forces giving up thread safety.

Here follows an example where an exception interrupts the function before std::cout can be restored from hexadecimal to decimal. The error number in the catch statement will be written out in hexadecimal which probably isn't what one wants:

#include <iostream>
#include <vector>

int main() {
  try {
    std::cout << std::hex;
    std::cout << 0xFFFFFFFF << std::endl;
    std::vector<int> vector(0xFFFFFFFFFFFFFFFFL, 0);  // Exception
    std::cout << std::dec;                            // Never reached
  } catch (std::exception &e) {
    std::cout << "Error number: " << 10 << std::endl;  // Not in decimal
  }
}

It is acknowledged even by some members of the C++ standards body that the iostreams interface is an aging interface that needs to be replaced eventually. This design forces the library implementers to adopt solutions that impact performance greatly.

Iterators

The philosophy of the Standard Template Library (STL) embedded in the C++ Standard Library is to use generic algorithms in the form of templates using iterators. Early compilers optimized small objects such as iterators poorly, which Alexander Stepanov characterized as the "abstraction penalty", although modern compilers optimize away such small abstractions well. The interface using pairs of iterators to denote ranges of elements has also been criticized. The C++20 standard library's introduction of ranges should solve this problem.

One big problem is that iterators often deal with heap allocated data in the C++ containers and become invalid if the data is independently moved by the containers. Functions that change the size of the container often invalidate all iterators pointing to it, creating dangerous cases of undefined behavior. Here is an example where the iterators in the for loop get invalidated because of the std::string container changing its size on the heap:

#include <iostream>
#include <string>

int main() {
  std::string text = "One\nTwo\nThree\nFour\n";
  // Let's add an '!' where we find newlines
  for (auto it = text.begin(); it != text.end(); ++it) {
    if (*it == '\n') {
      // it =
      text.insert(it, '!') + 1;
      // Without updating the iterator this program has
      // undefined behavior and will likely crash
    }
  }
  std::cout << text;
}

Uniform initialization syntax

The C++11 uniform initialization syntax and std::initializer_list share the same syntax which are triggered differently depending on the internal workings of the classes. If there is a std::initializer_list constructor then this is called. Otherwise the normal constructors are called with the uniform initialization syntax. This can be confusing for beginners and experts alike

#include <iostream>
#include <vector>

int main() {
  int integer1{10};                 // int
  int integer2(10);                 // int
  std::vector<int> vector1{10, 0};  // std::initializer_list
  std::vector<int> vector2(10, 0);  // size_t,int

  std::cout << "Will print 10" << std::endl << integer1 << std::endl;
  std::cout << "Will print 10" << std::endl << integer2 << std::endl;

  std::cout << "Will print 10,0," << std::endl;

  for (const auto& item : vector1) {
    std::cout << item << ',';
  }

  std::cout << std::endl;
  std::cout << "Will print 0,0,0,0,0,0,0,0,0,0," << std::endl;

  for (const auto& item : vector2) {
    std::cout << item << ',';
  }
}

Exceptions

There have been concerns that the zero-overhead principle isn't compatible with exceptions. Most modern implementations have a zero performance overhead when exceptions are enabled but not used, but do have an overhead during exception handling and in binary size due to the need to unroll tables. Many compilers support disabling exceptions from the language to save the binary overhead. Exceptions have also been criticized for being unsafe for state-handling. This safety issue has led to the invention of the RAII idiom, which has proven useful beyond making C++ exceptions safe.

Encoding of string literals in source-code

C++ string literals, like those of C, do not consider the character encoding of the text within them: they are merely a sequence of bytes, and the C++ string class follows the same principle. Although source code can (since C++11) request an encoding for a literal, the compiler does not attempt to validate that the chosen encoding of the source literal is "correct" for the bytes being put into it, and the runtime does not enforce character encoding. Programmers who are used to other languages such as Java, Python or C# which try to enforce character encodings often consider this to be a defect of the language.

The example program below illustrates the phenomenon.

#include <iostream>
#include <string>

int main() {
  // all strings are declared with the UTF-8 prefix
  std::string auto_enc = u8"Vår gård på Öland!";  // file encoding determines
                                                  // the encoding of å and Ö
  std::string ascii = u8"Var gard pa Oland!";     // this text is well-formed in
                                                  // both ISO-8859-1 and UTF-8
  std::string iso8859_1 =
      u8"V\xE5r g\xE5rd p\xE5 \xD6land!";  // explicitly use the ISO-8859-1
                                           // byte-values for å and Ö - this is
                                           // invalid UTF-8
  std::string utf8 =
      u8"V\xC3\xA5r g\xC3\xA5rd p\xC3\xA5 \xC3\x96land!";  // explicitly use the
                                                           // UTF-8 byte
                                                           // sequences for å
                                                           // and Ö - this will
                                                           // display
                                                           // incorrectly in
                                                           // ISO-8859-1
  std::cout << "byte-count of automatically-chosen, [" << auto_enc
            << "] = " << auto_enc.length() << '\n';
  std::cout << "byte-count of ASCII-only [" << ascii << "] = " << ascii.length()
            << '\n';
  std::cout << "byte-count of explicit ISO-8859-1 bytes [" << iso8859_1
            << "] = " << iso8859_1.length() << '\n';
  std::cout << "byte-count of explicit UTF-8 bytes [" << utf8
            << "] = " << utf8.length() << '\n';
}

Despite the presence of the C++11 'u8' prefix, meaning "Unicode UTF-8 string literal", the output of this program actually depends on the source file's text encoding (or the compiler's settings - most compilers can be told to convert source files to a specific encoding before compiling them). When the source file is encoded using UTF-8, and the output is run on a terminal that's configured to treat its input as UTF-8, the following output is obtained:

byte-count of automatically-chosen, [Vår gård på Öland!] = 22
byte-count of ASCII-only [Var gard pa Oland!] = 18
byte-count of explicit ISO-8859-1 bytes [Vr grd p land!] = 18
byte-count of explicit UTF-8 bytes [Vår gård på Öland!] = 22

The output terminal has stripped the invalid UTF-8 bytes from display in the ISO-8859 example string. Passing the program's output through a Hex_dump utility will reveal that they are still present in the program output, and it is the terminal application that removed them.

However, when the same source file is instead saved in ISO-8859-1 and re-compiled, the output of the program on the same terminal becomes:

byte-count of automatically-chosen, [Vr grd p land!] = 18
byte-count of ASCII-only [Var gard pa Oland!] = 18
byte-count of explicit ISO-8859-1 bytes [Vr grd p land!] = 18
byte-count of explicit UTF-8 bytes [Vår gård på Öland!] = 22

Code bloat

Some older implementations of C++ have been accused of generating code bloat.

See also

• Most vexing parse
• Function overloading § Complications
• Operator overloading § Criticisms
• Exception handling § Criticism
• Argument-dependent name lookup § Criticism
• Object slicing

References

Works cited

• Stroustrup, Bjarne (1994). The Design and Evolution of C++. Addison-Wesley. ISBN 0-201-54330-3. {{cite book}}: Invalid |ref=harv (help)

Further reading

• Ian Joyner (1999). Objects Unencapsulated: Java, Eiffel, and C++?? (Object and Component Technology). Prentice Hall PTR; 1st edition. ISBN 978-0130142696.
• Peter Seibel (2009). Coders at Work: Reflections on the Craft of Programming. Apress. ISBN 978-1430219484.

External links

• C++ FQA Lite by Yossi Kreinin
• C++ The COBOL of the 90s
• C++ in Coders at Work Excerpts from the book Coders at Work, by Peter Seibel
• DConf 2014: The Last Thing D Needs A video of a talk by Scott Meyers