C++

C++

Paradigm	multi-paradigm
Designed by	Bjarne Stroustrup
First appeared	1983 (1985 "The C++ Programming Language")
Typing discipline	Static, unsafe, nominative
Website	isocpp.org
Major implementations
GNU Compiler Collection, Microsoft Visual C++, Borland C++ Builder
Dialects
ISO/IEC C++ 1998, ISO/IEC C++ 2003
Influenced by
C, Simula, Ada 83, ALGOL 68, CLU, ML
Influenced
Ada 95, C#, Java, PHP, D, Aikido

C++ (pronounced "see plus plus", /siː plʌs plʌs/) is a general-purpose programming language with high-level and low-level capabilities. It is a statically typed, free-form, multi-paradigm, usually compiled language supporting procedural programming, data abstraction, object-oriented programming, and generic programming.

C++ is regarded as a mid-level language. This indicates that C++ comprises a combination of both high-level and low-level language features.

Dr. Bjarne Stroustrup developed C++ in 1979 at Bell Labs as an enhancement to the C programming language and named it "C with Classes". In 1983 it was renamed to C++. Enhancements started with the addition of classes, followed by, among other features, virtual functions, operator overloading, multiple inheritance, templates, and exception handling. The C++ programming language standard was ratified in 1998 as ISO/IEC 14882:1998, the current version of which is the 2003 version, ISO/IEC 14882:2003. A new version of the standard (known informally as C++0x) is being developed.

History

Stroustrup began work on C with Classes in 1979. The idea of creating a new language originated from Stroustrup's experience in programming for his Ph.D. thesis. Stroustrup found that Simula had features that were very helpful for large software development, but the language was too slow for practical use, while BCPL was fast but too low-level and unsuitable for large software development. When Stroustrup started working in Bell Labs, he had the problem of analyzing the UNIX kernel with respect to distributed computing. Remembering his Ph.D. experience, Stroustrup set out to enhance the C language with Simula-like features. C was chosen because it is general-purpose, fast, portable and widely used. Besides C and Simula, some other languages which inspired him were ALGOL 68, Ada, CLU and ML. At first, the class, derived class, strong type checking, inlining, and default argument features were added to C via Cfront. The first commercial release occurred in October 1985.

In 1983, the name of the language was changed from C with Classes to C++. New features were added including virtual functions, function name and operator overloading, references, constants, user-controlled free-store memory control, improved type checking, and BCPL style single-line comments with two forward slashes (//). In 1985, the first edition of The C++ Programming Language was released, providing an important reference to the language, as there was not yet an official standard. In 1989, Release 2.0 of C++ was released. New features included multiple inheritance, abstract classes, static member functions, const member functions, and protected members. In 1990, The Annotated C++ Reference Manual was published. This work became the basis for the future standard. Late addition of features included templates, exceptions, namespaces, new casts, and a Boolean type.

As the C++ language evolved, a standard library also evolved with it. The first addition to the C++ standard library was the stream I/O library which provided facilities to replace the traditional C functions such as printf and scanf. Later, among the most significant additions to the standard library, was the Standard Template Library.

Language standard

After years of work, a joint ANSI–ISO committee standardized C++ in 1998 (ISO/IEC 14882:1998). For some years after the official release of the standard, the committee processed defect reports, and published a corrected version of the C++ standard in 2003. In 2005, a technical report, called the "Library Technical Report 1" (often known as TR1 for short) was released. While not an official part of the standard, it gives a number of extensions to the standard library which are expected to be included in the next version of C++. Support for TR1 is growing in almost all currently maintained C++ compilers.

While the C++ language is royalty-free, the standard document itself is not freely available.

The name "C++"

This name is credited to Rick Mascitti (mid-1983) and was first used in December 1983. Earlier, during the research period, the developing language had been referred to as "new C", then "C with Classes". In computer science C++ is still referred to as a superstructure of C. The final name stems from C's "++" operator (which increments the value of a variable) and a common naming convention of using "+" to indicate an enhanced computer program. According to Stroustrup: "the name signifies the evolutionary nature of the changes from C". C+ was the name of an earlier, unrelated programming language.

Stroustrup addresses the origin of the name in Chapter 1 of his book, The C++ Programming Language, remarking that another interpretation of the C++ name could be seen from the appendix of George Orwell's Nineteen Eighty-Four. Of the three segments of the fictional language Newspeak, the "C vocabulary" is the one dedicated to technical terms and jargon. "Doubleplus" is the superlative modifier for Newspeak adjectives. Thus, "C++" might hold the meaning "most C-like" in Newspeak.

When Rick Mascitti was questioned informally in 1992 about the naming, he indicated that it was given in a tongue-in-cheek spirit. He never thought that it would become the formal name of the language.

Future development

C++ continues to evolve to meet future requirements. A new version of the C++ standard is currently being worked on, entitled C++0x, denoting that it is expected to be released before 2010. Current work indicates that C++ will continue to capitalize on its multi-paradigm nature. Notable expected improvements are native support for threading and concepts that will make working with templates easier. Adding garbage collection is currently under heavy discussion. Boost.org is a group working to make the most of C++ in its current form. They are expanding C++'s functional and metaprogramming abilities and also advise the C++ standards committee on which features work well and which need improving.

Philosophy

In The Design and Evolution of C++ (1994), Bjarne Stroustrup describes some rules that he uses for the design of C++. Knowing the rules helps to understand why C++ is the way it is. The following is a summary of the rules. Much more detail can be found in The Design and Evolution of C++.

• C++ is designed to be a statically typed, general-purpose language that is as efficient and portable as C
• C++ is designed to directly and comprehensively support multiple programming styles (procedural programming, data abstraction, object-oriented programming, and generic programming)
• C++ is designed to give the programmer choice, even if this makes it possible for the programmer to choose incorrectly
• C++ is designed to be as compatible with C as possible, therefore providing a smooth transition from C
• C++ avoids features that are platform specific or not general purpose
• C++ does not incur overhead for features that are not used
• C++ is designed to function without a sophisticated programming environment

Inside the C++ Object Model (Lippman, 1996) describes how compilers may convert C++ program statements into an in-memory layout. Compiler authors are free to implement the standard in their own manner.

Standard library

The 1998 ANSI/ISO C++ standard consists of two parts: the core language and the C++ standard library; the latter includes most of the Standard Template Library (STL) and a slightly modified version of the C standard library. Many C++ libraries exist which are not part of the standard, and, using linkage specification, libraries can even be written in languages such as C, Fortran, Pascal, or BASIC. Which of these are supported is compiler dependent.

The C++ standard library incorporates the C standard library with some small modifications to make it work better with the C++ language. Another large part of the C++ library is based on the STL. This provides such useful tools as containers (for example vectors and lists), iterators (generalized pointers) to provide these containers with array-like access and algorithms to perform operations such as searching and sorting. Furthermore (multi)maps (associative arrays) and (multi)sets are provided, all of which export compatible interfaces. Therefore it is possible, using templates, to write generic algorithms that work with any container or on any sequence defined by iterators. As in C, the features of the library are accessed by using the #include directive to include a standard header. C++ provides 69 standard headers, of which 19 are deprecated.

Using the standard library — for example, using std::vector or std::string instead of a C-style array — can help lead to safer and more scalable software.

The STL was originally a third-party library from HP and later SGI, before its incorporation into the C++ standard. The standard does not refer to it as "STL", as it is merely a part of the standard library, but many people still use that term to distinguish it from the rest of the library (input/output streams, internationalization, diagnostics, the C library subset, etc.).

Most C++ compilers provide an implementation of the C++ standard library, including the STL. Compiler-independent implementations of the STL, such as STLPort, also exist. Other projects also produce various custom implementations of the C++ standard library and the STL with various design goals.

Features introduced in C++

Compared to the C language, C++ introduced extra features, including declarations as statements, function-like casts, new/delete, bool, reference types, inline functions, default arguments, function and operator overloading, namespaces and the scope resolution (::) operator, classes (including all class-related features such as inheritance, member functions, virtual functions, abstract classes, and constructors), templates, exception handling, runtime type identification, and the overloaded input (>>) and output (<<) operators for input and output respectively.

Contrary to popular belief, C++ did not introduce the const keyword. Const was formally added to C shortly before it was adopted by C++.

C++ also performs more type checking than C in several cases (see "Incompatibility with C" below).

Double slash comments starting with // were originally part of C's predecessor, BCPL, and were reintroduced in C++.

Several features of C++ were later adopted by C, including declarations in for loops, C++-style comments (using the // symbol), and inline, though the C99 definition of the inline keyword is not compatible with its C++ definition. However, C99 also introduced features that do not exist in C++, such as variadic macros and better handling of arrays as parameters; some C++ compilers may implement some of these features as extensions, but others are incompatible with existing C++ features.

Hello world program

The following is a Hello world program which uses the C++ standard library stream facility to write a message to standard output.

#include <iostream> // provides std::cout
 
int main()
{
    std::cout << "Hello, world!\n";
    return 0;
}

Language features

Operators

Main article: Operators in C and C++

Preprocessor

C++ is principally compiled in three phases: preprocessing, translation to object code, and linking (the two last phases are what is generally thought of as the "compilation" proper). In the first phase, preprocessing, preprocessor directives apply lexical transformations to the source code, which is then fed to the compilation stage.

Preprocessor directives start with # as the first character on a line and before any spaces and work by simple substitution of tokenized character sequences for other character sequences or files, according to user-defined rules. They typically perform macro substitution, inclusion of other files (by opposition to higher-order features such as inclusion of modules/packages/units/components), conditional compilation and/or conditional inclusion. For instance:

#include <iostream>

which includes (imports) all symbols from the standard library header file iostream.

Another common use is what is commonly referred to as macros:

#define MY_ASSERT(x) assert(x)

which replaces MY_ASSERT(x) as it appears in the source code with assert(x). This allows control over the use of assertions in a particular compilation unit.

Using macro definitions to emulate functions however is discouraged in practice, as it doesn't allow any type checking for the parameters and the resulting code may introduce some pitfalls. Instead, the use of inline functions for this purpose is recommended.

In addition to these common directives there are several additional preprocessor directives that control the flow of compilation, conditionally include or exclude code blocks, and control various other aspects of compilation.

Traditionally the preprocessor was also used to define numerical constants, however the use of const is now preferred over #define. This provides stronger type checking and does not subvert the use of namespaces as the preprocessor does.

The goal of the standardization committee is to reduce dependency on the preprocessor. Because C++'s modular nature requires support for such directives as #include and #define, it is unlikely that it will be completely eliminated.

See also: preprocessor and C preprocessor

Templates

See also: generic programming and template metaprogramming

Templates are different from macros: while both of these compile-time language features can be used to produce conditional compilation, templates are not restricted to lexical substitution. Templates have an awareness of the semantics and type system of their companion language as well as all compile-time type definitions and can perform high-level operations including programmatic flow control based on evaluation of strictly type-checked parameters. Macros are capable of conditional control over compilation based on predetermined criteria but cannot instantiate new types, recurse or perform type evaluation and in effect are limited to pre-compilation text-substitution and text-inclusion/exclusion. In other words, macros can control compilation flow based on pre-defined symbols but cannot, unlike templates, independently instantiate new symbols. Templates are a tool for static polymorphism (see below) and generic programming. For example, a template replacing the common, but dangerous, macro #define max(x,y) ((x)>(y)?(x):(y)):

template <typename T>
T max(const T& x, const T& y)
{
    return x > y ? x : y;
}

This can be found in the algorithm header as std::max(). Traditionally the keyword class may also be used in place of typename.

In addition, templates are a compile time mechanism in C++ which is Turing-complete, meaning that any computation expressible by a computer program can be computed, in some form, by a template metaprogram prior to runtime.

In summary defining a template for a function or class is the equivalent of defining a function or class for each type that can be used as argument, but does not require forward knowledge of which types will be used.

Objects

C++ introduces some object-oriented (OO) features to C. It offers classes, which provide the four features commonly present in OO (and some non-OO) languages: abstraction, encapsulation, inheritance and polymorphism. Objects are instances of classes created at runtime. Think of the class as a template from which many different individual objects may be generated as a program runs.

Encapsulation

Encapsulation is the grouping together of data and functionality. C++ implements encapsulation by allowing all members of a class to be declared as either public, private, or protected. A public member of the class will be accessible to any function. A private member will only be accessible to functions that are members of that class and to functions and classes explicitly granted access permission by the class ("friends"). A protected member will be accessible to members of classes that inherit from the class in addition to the class itself and any friends.

The OO principle is that all and only the functions that can access the internal representation of a type should be encapsulated within the type definition. C++ supports this (via member functions and friend functions), but does not enforce it: the programmer can declare parts or all of the representation of a type to be public, and is also allowed to make public entities that are not part of the representation of the type. Because of this, C++ supports not just OO programming but other weaker decomposition paradigms, like modular programming.

It is generally considered good practice to make all data private or protected, and to make public only those functions that are part of a minimal interface for users of the class, that hides implementation details.

Inheritance

Inheritance allows one data type to acquire properties of other data types. Inheritance from a base class may be declared as public, protected, or private. This access specifier determines whether unrelated and derived classes can access the inherited public and protected members of the base class. Only public inheritance corresponds to what is usually meant by "inheritance". The other two forms are much less frequently used. If the access specifier is omitted, inheritance is assumed to be private for a class base and public for a struct base. Base classes may be declared as virtual; this is called virtual inheritance. Virtual inheritance ensures that only one instance of a base class exists in the inheritance graph, avoiding some of the ambiguity problems of multiple inheritance.

Multiple inheritance is a C++ feature sometimes considered controversial. Multiple inheritance allows a class to be derived from more than one base class; this can result in a complicated graph of inheritance relationships. For example, a "Flying Cat" class can inherit from both "Cat" and "Flying Mammal". Some other languages, such as C# or Java, accomplish something similar (although more limited) by allowing inheritance of multiple interfaces while restricting the number of base classes to one (interfaces, unlike classes, provide only declarations of member functions, no implementation or member data).

Polymorphism

See also: Polymorphism in object-oriented programming

Polymorphism enables one common interface for many implementations, and for objects to act differently under different circumstances.

C++ supports several kinds of static (compile-time) and dynamic (run-time) polymorphism. Compile-time polymorphism does not allow for certain run-time decisions, while run-time polymorphism typically incurs a performance penalty.

Static polymorphism

Function overloading

Function overloading allows programs to declare multiple functions having the same name (but with different arguments). The functions are distinguished by the number and/or types of their formal parameters. Thus, the same function name can refer to different functions depending on the context in which it is used. The type returned by the function is not used to distinguish overloaded functions.

Operator overloading

Similarly, operator overloading allows programs to define certain operators (such as +, !=, <, or &) to result in a function call that depends on the types of the operands they are used on. Overloading an operator does not change the precedence of calculations involving the operator, nor does it change the number of operands that the operator uses (any operand may however be ignored). The . :: .* ? operators can not be overloaded.

Default arguments

Default arguments are used when defining a different function is not needed when supplying a default value for an argument will suffice. Care should be taken when using default arguments in conjunction with overloaded functions to not cause a conflict over which function to use. For instance, the following code:

// function with default argument but also an overloaded function
int strcpy(char *str1, char *str2, short unsigned n=65535);
// second overloaded function
int strcpy(char *str1, char *str2);

will compile correctly when strcpy is used with an argument for n but not when no argument is specified. This is because the compiler has no means of knowing if the intended function is the first form with a default value of 65535 for n or the second form with no n argument .

Class and function templates

Templates in C++ provide a sophisticated mechanism for writing generic, polymorphic code. In particular, through the Curiously Recurring Template Pattern it's possible to implement a form of static polymorphism that closely mimics the syntax for overriding virtual methods (a dynamic polymorphism technique described below). Since C++ templates are type-aware and Turing-complete they can also be used to let the compiler resolve recursive conditionals and generate substantial programs through template metaprogramming.

Dynamic polymorphism

Inheritance

Variable pointers (and references) of a base class type in C++ can refer to objects of any derived classes of that type in addition to objects exactly matching the variable type. This allows arrays and other kinds of containers to hold pointers to objects of differing types. Because assignment of values to variables usually occurs at run-time, this is necessarily a run-time phenomenon.

C++ also provides a dynamic_cast operator, which allows the program to safely attempt conversion of an object into an object of a more specific object type (as opposed to conversion to a more general type, which is always allowed). This feature relies on run-time type information (RTTI). Objects known to be of a certain specific type can also be cast to that type with static_cast, a purely compile-time construct which is faster and does not require RTTI.

Virtual member functions

Ordinarily when a method in a derived class overrides a method in a base class the method to call is determined by the type of the object. Methods are overridden when, unlike with function overloading, there exists no distinction between the parameters for a given method in number or type. By virtue of inherited objects being polymorphic, it may not be possible for the compiler to determine the type of the object and therefore the correct function to call at compile time and the decision is therefore put off until runtime. This is called dynamic dispatch. Virtual member functions or methods allow the most specific implementation of the function to be called, according to the actual run-time type of the object. In C++, this is commonly done using virtual function tables. This may sometimes be bypassed by prepending a fully qualified class name before the function call, but calls to virtual functions are in general always resolved at run time.

In addition to standard member functions, operator overloads and destructors can also be virtual. A general rule of thumb is that if any functions in the class are virtual, the destructor should be as well. As the type of an object at its creation is known at compile time, constructors, and by extention copy constructors, can not be virtual. Nontheless a situation may arise where a copy of an object needs to be created when a pointer to a derived object is passed as a pointer to a base object. In such a case a common solution is to create a Clone() (or similar) method and declare that as virtual. The Clone() method creates and returns a copy of the derived class when called.

A member function can also be made "pure virtual" by appending it with = 0 after the closing bracket and before the semicolon. Objects can not be created of a class with a pure virtual function and are called abstract data types. Such abstract data types can only be derived from. Any derived class inherits the virtual function as pure and must override it (and all other pure virtual functions) with a non-pure virtual function for objects to be created from the derived class. An attempt to create an object from a class with a pure virtual function or inherited pure virtual function will be flagged as a compile-time error.

An example:

#include <iostream>

class Bird                 // the "generic" base class
{
public:
  virtual void OutputName() {std::cout << "a bird";}
  virtual ~Bird() {}
};
 
class Swan : public Bird   // Swan derives from Bird
{ 
public:
  void OutputName() {std::cout << "a swan";} // overrides virtual function
};
 
int main()
{
  Swan mySwan;            // Creates a swan.

  Bird* myBird = &mySwan;  // Declares a pointer to a generic Bird,
                           // and sets it pointing to a newly created Swan.

  myBird->OutputName();    // This will output "a swan", not "a bird".

  return 0;
}

This example program makes use of virtual functions, polymorphism, and inheritance to derive new, more specific objects from a base class. In this case, the base class is a Bird, and the more specific Swan is made.

Parsing and processing C++ source code

It is relatively difficult to write a good C++ parser with classic parsing algorithms such as LALR(1) (see [1]). This is partly because the C++ grammar is not LALR. Because of this, there are very few tools for analyzing or performing non-trivial transformations (e.g., refactoring) of existing code. One way to handle this difficulty is to choose a different syntax, such as Significantly Prettier and Easier C++ Syntax, which is LALR(1) parsable. More powerful parsers, such as GLR parsers, can be substantially simpler (though slower).

Parsing (in the literal sense of producing a syntax tree) is not the most difficult problem in building a C++ processing tool. Such tools must also have the same understanding of the meaning of the identifiers in the program as a compiler might have. Practical systems for processing C++ must then not only parse the source text, but be able to resolve for each identifier precisely which definition applies (e.g. they must correctly handle C++'s complex scoping rules) and what its type is, as well as the types of larger expressions.

Finally, a practical C++ processing tool must be able to handle the variety of C++ dialects used in practice (such as GNU's and Microsoft's) and implement appropriate analyzers, source code transformers, and regenerate source text. Combining advanced parsing algorithms such as GLR with symbol table construction and program transformation machinery can enable the construction of arbitrary C++ tools.

Problems and controversies

Standards compliance

Traditionally, producing a reasonably standards-compliant C++ compiler has proven to be a difficult task for compiler vendors in general. For many years, different C++ compilers implemented the C++ language to different levels of compliance to the standard, and their implementations varied widely in some areas such as partial template specialization. Recent releases of most popular C++ compilers support almost all of the C++ 1998 standard.

One particular point of contention is the export keyword, intended to allow template definitions to be separated from their declarations. The first compiler to implement export was Comeau C++, in early 2003 (5 years after the release of the standard); in 2004, the beta compiler of Borland C++ Builder X was also released with export. Both of these compilers are based on the EDG C++ front end. It should also be noted that many C++ books provide example code using the keyword export (for example, Beginning ANSI C++ by Ivor Horton) which will not compile in most compilers, but there is no reference to the problem with the keyword export mentioned. Other compilers such as GCC do not support it at all. Herb Sutter, secretary of the C++ standards committee, recommended that export be removed from future versions of the C++ standard, but finally the decision was made to retain it.

In order to give compiler vendors greater freedom, the C++ standards committee decided not to dictate the implementation of name mangling, exception handling, and other implementation-specific features. The downside of this decision is that object code produced by different compilers are expected to be incompatible. There are, however, third party standards for particular machines or operating systems which attempt to standardize compilers on those platforms (for example C++ ABI); some compilers adopt a secondary standard for these items.

Criticism

Modern critics of the language raise several points. First, since C++ is based on and largely compatible with C, it inherits most of the criticisms leveled at that language. Taken as a whole C++ has a large feature set, including all of C, plus a large set of its own additions, in part leading to criticisms of being a "bloated" and complicated language, especially for embedded systems due to features such as exceptions and RTTI which add to code size. However, every compiler allows the developer to disable exceptions if desired. Bjarne Stroustrup also points out that resultant executables don't support these claims of bloat: "I have even seen the C++ version of the 'hello world' program smaller than the C version." The Embedded C++ standard was specified to deal with part of this, but it received criticism for leaving out useful parts of the language that incur no runtime penalty. Because of its large featureset it can be quite difficult to fully master C++, leading to programmers often bringing unnecessarily advanced or complicated solutions to simple problems.

While C++ is more complex than some other programming languages, Bjarne Stroustrup points out that "The programming world is far more complex today than it was 30 years ago, and modern programming languages reflect that." The ISO standard of the C++ language is about 310 pages (excluding library). For comparison, the C programming language's is about 160 pages, even though it was designed more than 15 years prior and doesn't consider Object Oriented Programming. Furthermore, C#'s ECMA language definition document is about 440 pages.

C++ is also sometimes compared unfavorably with single-paradigm object-oriented languages such as Java, on the basis that it allows programmers to "mix and match" object-oriented and procedural programming, rather than strictly enforcing a single paradigm. This is part of a wider debate on the relative merits of the two programming styles.

Incompatibility with C

Further information: Compatibility of C and C++

C++ is often considered to be a superset of C, but this is not strictly true. Most C code can easily be made to compile correctly in C++, but there are a few differences that cause some valid C code to be invalid in C++, or to behave differently in C++.

One commonly encountered difference is that C allows implicit conversion from void* to other pointer types, but C++ does not. So, the following is valid C code:

int *i = malloc(sizeof(int) * 5);     /* Implicit conversion from void* to int* */

... but to make it work in both C and C++ one would need to use an explicit cast:

int *i = (int *) malloc(sizeof(int) * 5);

...and in C++-only code, the static cast is recommended:

int *i = static_cast<int*>(malloc(sizeof(int) * 5));

Another common portability issue is that C++ defines many new keywords, such as new and class, that may be used as identifiers (e.g. variable names) in a C program.

Some incompatibilities have been removed by the latest (C99) C standard, which now supports C++ features such as // comments and mixed declarations and code. However, C99 introduced a number of new features that C++ does not support (such as variable-length arrays, native complex-number types, and compound literals), so the languages may be diverging more than they are converging. (However, at least some of the new C99 features will likely be included in the next version of the C++ standard, C++0x.)

In order to intermix C and C++ code, any C code which is to be called from/used in C++ must be declared with C linkage by placing it within an extern "C" { ... } block.

See also

• C++ structures and classes
• List of C++ compilers and integrated development environments
• Visual C++
• Boost C++ Libraries - Selection of C++ libraries designed to work with the standard C++ library
• CodeSynthesis XSD - An open-source XML data binding framework for C++
• Name mangling
• Template metaprogramming
• Comparison of Java and C++
• Comparison of programming languages
• Aard - A programming tool to check memory usage of C++ programs
• Aikido - Scripting language with C++ like syntax

General references

• Abrahams, David. C++ Template Metaprogramming: Concepts, Tools, and Techniques from Boost and Beyond. Addison-Wesley. ISBN 0-321-22725-5. {{cite book}}: Unknown parameter |coauthors= ignored (|author= suggested) (help)
• Alexandrescu, Andrei (2001). Modern C++ Design: Generic Programming and Design Patterns Applied. Addison-Wesley. ISBN 0-201-70431-5.
• Becker, Pete (2006). The C++ Standard Library Extensions : A Tutorial and Reference. Addison-Wesley. ISBN 0-321-41299-0.
• Alexandrescu, Andrei (2004). C++ Design and Coding Standards: Rules and Guidelines for Writing Programs. Addison-Wesley. ISBN 0-321-11358-6. {{cite book}}: Unknown parameter |coauthors= ignored (|author= suggested) (help)
• Coplien, James O. (1992, reprinted with corrections 1994). Advanced C++: Programming Styles and Idioms. ISBN 0-201-54855-0. {{cite book}}: Check date values in: |year= (help)CS1 maint: year (link)
• Dewhurst, Stephen C. (2005). C++ Common Knowledge: Essential Intermediate Programming. Addison-Wesley. ISBN 0-321-32192-8.
• Information Technology Industry Council (2003-10-15). Programming languages — C++ (Second edition ed.). Geneva: ISO/IEC. 14882:2003(E). {{cite book}}: |edition= has extra text (help); Check date values in: |date= (help)
• Josuttis, Nicolai M. The C++ Standard Library. Addison-Wesley. ISBN 0-201-37926-0.
• Koenig, Andrew (2000). Accelerated C++ - Practical Programming by Example. Addison-Wesley. ISBN 0-201-70353-X. {{cite book}}: Unknown parameter |coauthors= ignored (|author= suggested) (help)
• Lippman, Stanley B. (2005). C++ Primer. Addison-Wesley. ISBN 0-201-72148-1. {{cite book}}: Unknown parameter |coauthors= ignored (|author= suggested) (help)
• Lippman, Stanley B. (1996). Inside the C++ Object Model. Addison-Wesley. ISBN 0-201-83454-5.
• Stroustrup, Bjarne (2000). The C++ Programming Language (Special Edition ed.). Addison-Wesley. ISBN 0-201-70073-5. {{cite book}}: |edition= has extra text (help)
• Stroustrup, Bjarne (1994). The Design and Evolution of C++. Addison-Wesley. ISBN 0-201-54330-3.
• Sutter, Herb (2001). More Exceptional C++: 40 New Engineering Puzzles, Programming Problems, and Solutions. Addison-Wesley. ISBN 0-201-70434-X.
• Sutter, Herb (2004). Exceptional C++ Style. Addison-Wesley. ISBN 0-201-76042-8.
• Vandevoorde, David (2003). C++ Templates: The complete Guide. Addison-Wesley. ISBN 0-201-73484-2. {{cite book}}: Unknown parameter |coauthors= ignored (|author= suggested) (help)

External links

• A paper by Stroustrup showing the timeline of C++ evolution (1979-1991)
• Open Directory on C++
• Apache C++ Standard Library Documentation
• Dinkumware's C++ Library Reference Manual
• C/C++ Reference
• Standards Committee Page: JTC1/SC22/WG21 - C++
• CodePedia C++ main page
• A Compiler-Comparison chart
• C++ FAQ Lite by Marshall Cline
• comp.lang.c++, comp.lang.c++.moderated, comp.std.c++ Newsgroups
• C++ Tutorial Links