Difference between revisions of "C++"

== History ==

== History ==

In 1979, [[Bjarne Stroustrup]], a Danish [[computer scientist]], began work on "{{visible anchor|C with [[Class (computer programming)|Classes]]}}", the predecessor to C++.<ref name="invention3">{{cite web |url = http://www.stroustrup.com/bs_faq.html#invention|title = Bjarne Stroustrup's FAQ: When was C++ invented?|first = Bjarne|last = Stroustrup|website = stroustrup.com|date = 7 March 2010|accessdate = 16 September 2010}}

In 1979, [[Bjarne Stroustrup]], a Danish [[computer scientist]], began work on "{{visible anchor|C with [[Class (computer programming)|Classes]]}}", the predecessor to C++.<ref name="invention3">{{cite web |url = http://www.stroustrup.com/bs_faq.html#invention|title = Bjarne Stroustrup's FAQ: When was C++ invented?|first = Bjarne|last = Stroustrup|website = stroustrup.com|date = 7 March 2010|accessdate = 16 September 2010}}

Initially, Stroustrup's "C with Classes" added features to the C compiler, Cpre, including [[class (computer programming)|classes]], [[derived class]]es, [[strong typing]], [[inlining]] and [[default argument]]s.<ref name="hopl2">{{cite web|last1=Stroustrup|first1=Bjarne|title=A History of C ++ : 1979− 1991|url=http://www.stroustrup.com/hopl2.pdf}}</ref>

Initially, Stroustrup's "C with Classes" added features to the C compiler, Cpre, including [[class (computer programming)|classes]], [[derived class]]es, [[strong typing]], [[inlining]] and [[default argument]]s.<ref name="hopl2">{{cite web|last1=Stroustrup|first1=Bjarne|title=A History of C ++ : 1979− 1991|url=http://www.stroustrup.com/hopl2.pdf}}</ref>

In 1985, the first edition of ''[[The C++ Programming Language]]'' was released, which became the definitive reference for the language, as there was not yet an official standard.<ref name="1st-edition3">{{cite web |url = http://www.stroustrup.com/1st.html|title = The C++ Programming Language|edition = First|first = Bjarne|last = Stroustrup|accessdate = 16 September 2010}}

In 1985, the first edition of ''[[The C++ Programming Language]]'' was released, which became the definitive reference for the language, as there was not yet an official standard.<ref name="1st-edition3">{{cite web |url = http://www.stroustrup.com/1st.html|title = The C++ Programming Language|edition = First|first = Bjarne|last = Stroustrup|accessdate = 16 September 2010}}

</ref> The first commercial implementation of C++ was released in October of the same year.<ref name="invention3"/>

</ref> The first commercial implementation of C++ was released in October of the same year.<ref name="invention3"/>

=== Etymology ===

=== Etymology ===

=== Philosophy ===

=== Philosophy ===

=== Standardization ===

=== Standardization ===

{| class="wikitable floatright" style="margin-left: 1.5em;"

{| class="wikitable floatright" style="margin-left: 1.5em;"

|-

|-

|-

|-

! 1998

! 1998

|-

|-

! 2003

! 2003

|-

|-

! 2020

! 2020

|}

|}

C++ is standardized by an [[International Organization for Standardization|ISO]] working group known as [[ISO/IEC JTC 1/SC 22|JTC1/SC22/WG21]]. So far, it has published five revisions of the C++ standard and is currently working on the next revision, [[C++20]].

C++ is standardized by an [[International Organization for Standardization|ISO]] working group known as [[ISO/IEC JTC 1/SC 22|JTC1/SC22/WG21]]. So far, it has published five revisions of the C++ standard and is currently working on the next revision, [[C++20]].

The next major revision of the standard was informally referred to as "C++0x", but it was not released until 2011.<ref name="0xapprove">{{cite web|url=https://herbsutter.com/2011/08/12/we-have-an-international-standard-c0x-is-unanimously-approved/|title=We have an international standard: C++0x is unanimously approved|website=Sutter's Mill}}</ref>  [[C++11]] (14882:2011) included many additions to both the core language and the standard library.<ref name="isocpp2011"/>

The next major revision of the standard was informally referred to as "C++0x", but it was not released until 2011.<ref name="0xapprove">{{cite web|url=https://herbsutter.com/2011/08/12/we-have-an-international-standard-c0x-is-unanimously-approved/|title=We have an international standard: C++0x is unanimously approved|website=Sutter's Mill}}</ref>  [[C++11]] (14882:2011) included many additions to both the core language and the standard library.<ref name="isocpp2011"/>

== Language ==

== Language ==

C++ inherits most of [[C syntax|C's syntax]]. The following is Bjarne Stroustrup's version of the [[Hello world program]] that uses the [[C++ Standard Library]] stream facility to write a message to [[Standard output#Standard output (stdout)|standard output]]:<ref>{{Cite book |first=Bjarne |last=Stroustrup |year=2000 |page=46 |title=The C++ Programming Language |edition=Special |publisher=Addison-Wesley |isbn=0-201-70073-5 }}</ref><ref>{{cite web |url=http://www.stroustrup.com/3rd_issues.html |title=Open issues for The C++ Programming Language (3rd Edition) |first=Bjarne |last=Stroustrup |postscript=. This code is copied directly from Bjarne Stroustrup's errata page (p. 633). He addresses the use of <code>'\n'</code> rather than <code>std::endl</code>. Also see [http://www.stroustrup.com/bs_faq2.html#void-main Can I write "void main()"?] for an explanation of the implicit <code>return 0;</code> in the <code>main</code> function. This implicit return is ''not'' available in other functions.}}</ref>

C++ inherits most of [[C syntax|C's syntax]]. The following is Bjarne Stroustrup's version of the [[Hello world program]] that uses the [[C++ Standard Library]] stream facility to write a message to [[Standard output#Standard output (stdout)|standard output]]:<ref>{{Cite book |first=Bjarne |last=Stroustrup |year=2000 |page=46 |title=The C++ Programming Language |edition=Special |publisher=Addison-Wesley |isbn=0-201-70073-5 }}</ref><ref>{{cite web |url=http://www.stroustrup.com/3rd_issues.html |title=Open issues for The C++ Programming Language (3rd Edition) |first=Bjarne |last=Stroustrup |postscript=. This code is copied directly from Bjarne Stroustrup's errata page (p. 633). He addresses the use of <code>'\n'</code> rather than <code>std::endl</code>. Also see [http://www.stroustrup.com/bs_faq2.html#void-main Can I write "void main()"?] for an explanation of the implicit <code>return 0;</code> in the <code>main</code> function. This implicit return is ''not'' available in other functions.}}</ref>

* Yes, you could use "printf" from the Standard C Library.

* Yes, you could use "printf" from the Standard C Library.

*

*

*

*

* The latest consensus is ''not'' to make any of those changes.

* The latest consensus is ''not'' to make any of those changes.

***************************************************************

***************************************************************

#include <iostream>

#include <iostream>

     std::cout << "Hello, world!\n";

     std::cout << "Hello, world!\n";

}

}

*** PLEASE NOTE:****

*** PLEASE NOTE:****

=== Object storage ===

=== Object storage ===

==== Static storage duration objects ====

==== Static storage duration objects ====

Static storage duration objects are initialized in two phases. First, "static initialization" is performed, and only ''after'' all static initialization is performed, "dynamic initialization" is performed.  In static initialization, all objects are first initialized with zeros; after that, all objects that have a constant initialization phase are initialized with the constant expression (i.e. variables initialized with a literal or <code>constexpr</code>). Though it is not specified in the standard, the static initialization phase can be completed at compile time and saved in the data partition of the executable.  Dynamic initialization involves all object initialization done via a constructor or function call (unless the function is marked with <code>constexpr</code>, in C++11). The dynamic initialization order is defined as the order of declaration within the compilation unit (i.e. the same file). No guarantees are provided about the order of initialization between compilation units.

Static storage duration objects are initialized in two phases. First, "static initialization" is performed, and only ''after'' all static initialization is performed, "dynamic initialization" is performed.  In static initialization, all objects are first initialized with zeros; after that, all objects that have a constant initialization phase are initialized with the constant expression (i.e. variables initialized with a literal or <code>constexpr</code>). Though it is not specified in the standard, the static initialization phase can be completed at compile time and saved in the data partition of the executable.  Dynamic initialization involves all object initialization done via a constructor or function call (unless the function is marked with <code>constexpr</code>, in C++11). The dynamic initialization order is defined as the order of declaration within the compilation unit (i.e. the same file). No guarantees are provided about the order of initialization between compilation units.

==== Thread storage duration objects ====

==== Thread storage duration objects ====

==== Automatic storage duration objects ====

==== Automatic storage duration objects ====

Local variables are created as the point of execution passes the declaration point. If the variable has a constructor or initializer this is used to define the initial state of the object. Local variables are destroyed when the local block or function that they are declared in is closed. C++ destructors for local variables are called at the end of the object lifetime, allowing a discipline for automatic resource management termed [[Resource Acquisition Is Initialization|RAII]], which is widely used in C++.

Local variables are created as the point of execution passes the declaration point. If the variable has a constructor or initializer this is used to define the initial state of the object. Local variables are destroyed when the local block or function that they are declared in is closed. C++ destructors for local variables are called at the end of the object lifetime, allowing a discipline for automatic resource management termed [[Resource Acquisition Is Initialization|RAII]], which is widely used in C++.

==== Dynamic storage duration objects ====

==== Dynamic storage duration objects ====

=== Templates ===

=== Templates ===

{{See also|Template metaprogramming|Generic programming}}

{{See also|Template metaprogramming|Generic programming}}

Templates are different from [[Macro (computer science)|macro]]s: while both of these compile-time language features enable conditional compilation, templates are not restricted to lexical substitution. Templates are aware 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 in object-oriented programming|polymorphism]] (see below) and [[generic programming]].

Templates are different from [[Macro (computer science)|macro]]s: while both of these compile-time language features enable conditional compilation, templates are not restricted to lexical substitution. Templates are aware 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 in object-oriented programming|polymorphism]] (see below) and [[generic programming]].

=== Objects ===

=== Objects ===

C++ introduces [[object-oriented programming]] (OOP) features to C. It offers [[class (computer science)|class]]es, which provide the four features commonly present in OOP (and some non-OOP) languages: [[Abstraction (computer science)|abstraction]], [[Information hiding|encapsulation]], [[Inheritance (object-oriented programming)|inheritance]], and [[Polymorphism (computer science)|polymorphism]]. One distinguishing feature of C++ classes compared to classes in other programming languages is support for deterministic [[destructor (computer science)|destructors]], which in turn provide support for the [[Resource Acquisition is Initialization]] (RAII) concept.

C++ introduces [[object-oriented programming]] (OOP) features to C. It offers [[class (computer science)|class]]es, which provide the four features commonly present in OOP (and some non-OOP) languages: [[Abstraction (computer science)|abstraction]], [[Information hiding|encapsulation]], [[Inheritance (object-oriented programming)|inheritance]], and [[Polymorphism (computer science)|polymorphism]]. One distinguishing feature of C++ classes compared to classes in other programming languages is support for deterministic [[destructor (computer science)|destructors]], which in turn provide support for the [[Resource Acquisition is Initialization]] (RAII) concept.

The object-oriented principle ensures the encapsulation of all and only the functions that access the internal representation of a type. C++ supports this principle via member functions and friend functions, but it does not enforce it. Programmers can declare parts or all of the representation of a type to be public, and they are allowed to make public entities not part of the representation of a type. Therefore, C++ supports not just object-oriented programming, but other decomposition paradigms such as [[Modularity (programming)|modular programming]].

The object-oriented principle ensures the encapsulation of all and only the functions that access the internal representation of a type. C++ supports this principle via member functions and friend functions, but it does not enforce it. Programmers can declare parts or all of the representation of a type to be public, and they are allowed to make public entities not part of the representation of a type. Therefore, C++ supports not just object-oriented programming, but other decomposition paradigms such as [[Modularity (programming)|modular programming]].

==== Inheritance ====

==== Inheritance ====

| {{C-lang| typeid}}

| {{C-lang| typeid}}

|}

|}

C++ provides more than 35 operators, covering basic arithmetic, bit manipulation, indirection, comparisons, logical operations and others. Almost all operators can be [[Operator overloading|overloaded]] for user-defined types, with a few notable exceptions such as member access (<code>.</code> and <code>.*</code>) as well as the conditional operator. The rich set of overloadable operators is central to making user-defined types in C++ seem like built-in types.

C++ provides more than 35 operators, covering basic arithmetic, bit manipulation, indirection, comparisons, logical operations and others. Almost all operators can be [[Operator overloading|overloaded]] for user-defined types, with a few notable exceptions such as member access (<code>.</code> and <code>.*</code>) as well as the conditional operator. The rich set of overloadable operators is central to making user-defined types in C++ seem like built-in types.

{{See also|Subtyping}}

{{See also|Subtyping}}

C++ also provides the <syntaxhighlight lang="C++" inline>dynamic_cast</syntaxhighlight> operator, which allows code to safely attempt conversion of an object, via a base reference/pointer, to a more derived type: ''downcasting''. The ''attempt'' is necessary as often one does not know which derived type is referenced. (''Upcasting'', conversion to a more general type, can always be checked/performed at compile-time via <syntaxhighlight lang="C++" inline>static_cast</syntaxhighlight>, as ancestral classes are specified in the derived class's interface, visible to all callers.) <syntaxhighlight lang="C++" inline>dynamic_cast</syntaxhighlight> relies on [[run-time type information]] (RTTI), metadata in the program that enables differentiating types and their relationships. If a <syntaxhighlight lang="C++" inline>dynamic_cast</syntaxhighlight> to a pointer fails, the result is the <syntaxhighlight lang="C++" inline>nullptr</syntaxhighlight> constant, whereas if the destination is a reference (which cannot be null), the cast throws an exception. Objects ''known'' to be of a certain derived type can be cast to that with <syntaxhighlight lang="C++" inline>static_cast</syntaxhighlight>, bypassing RTTI and the safe runtime type-checking of <syntaxhighlight lang="C++" inline>dynamic_cast</syntaxhighlight>, so this should be used only if the programmer is very confident the cast is, and will always be, valid.

C++ also provides the <syntaxhighlight lang="C++" inline>dynamic_cast</syntaxhighlight> operator, which allows code to safely attempt conversion of an object, via a base reference/pointer, to a more derived type: ''downcasting''. The ''attempt'' is necessary as often one does not know which derived type is referenced. (''Upcasting'', conversion to a more general type, can always be checked/performed at compile-time via <syntaxhighlight lang="C++" inline>static_cast</syntaxhighlight>, as ancestral classes are specified in the derived class's interface, visible to all callers.) <syntaxhighlight lang="C++" inline>dynamic_cast</syntaxhighlight> relies on [[run-time type information]] (RTTI), metadata in the program that enables differentiating types and their relationships. If a <syntaxhighlight lang="C++" inline>dynamic_cast</syntaxhighlight> to a pointer fails, the result is the <syntaxhighlight lang="C++" inline>nullptr</syntaxhighlight> constant, whereas if the destination is a reference (which cannot be null), the cast throws an exception. Objects ''known'' to be of a certain derived type can be cast to that with <syntaxhighlight lang="C++" inline>static_cast</syntaxhighlight>, bypassing RTTI and the safe runtime type-checking of <syntaxhighlight lang="C++" inline>dynamic_cast</syntaxhighlight>, so this should be used only if the programmer is very confident the cast is, and will always be, valid.

C++ provides support for [[anonymous function]]s, also known as lambda expressions, with the following form:

C++ provides support for [[anonymous function]]s, also known as lambda expressions, with the following form:

[capture](parameters) -> return_type { function_body }

[capture](parameters) -> return_type { function_body }

=== Exception handling ===

=== Exception handling ===

Exception handling is used to communicate the existence of a runtime problem or error from where it was detected to where the issue can be handled.<ref>{{Cite web|url = http://www.cl.cam.ac.uk/teaching/1314/CandC++/lecture7.pdf|title = <nowiki>C and C++ Exceptions | Templates</nowiki>|date = 2013|accessdate = 30 August 2016|website = Cambridge Computer Laboratory - Course Materials 2013-14|publisher = |last = Mycroft|first = Alan}}</ref> It permits this to be done in a uniform manner and separately from the main code, while detecting all errors.<ref name="exception_summary">{{Cite book|title = The C++ Programming Language|last = Stroustrup|first = Bjarne|publisher = Addison Wesley|year = 2013|isbn = 9780321563842|location = |pages = 345}}</ref> Should an error occur, an exception is thrown (raised), which is then caught by the nearest suitable exception handler. The exception causes the current scope to be exited, and also each outer scope (propagation) until a suitable handler is found, calling in turn the destructors of any objects in these exited scopes.<ref>{{Cite book|title = The C++ Programming Language|last = Stroustrup|first = Bjarne|publisher = Addison Wesley|year = 2013|isbn = 9780321563842|location = |pages = 363–365}}</ref> At the same time, an exception is presented as an object carrying the data about the detected problem.<ref>{{Cite book|title = The C++ Programming Language|last = Stroustrup|first = Bjarne|publisher = Addison Wesley|year = 2013|isbn = 9780321563842|location = |pages = 345, 363}}</ref>

Exception handling is used to communicate the existence of a runtime problem or error from where it was detected to where the issue can be handled.<ref>{{Cite web|url = http://www.cl.cam.ac.uk/teaching/1314/CandC++/lecture7.pdf|title = <nowiki>C and C++ Exceptions | Templates</nowiki>|date = 2013|accessdate = 30 August 2016|website = Cambridge Computer Laboratory - Course Materials 2013-14|publisher = |last = Mycroft|first = Alan}}</ref> It permits this to be done in a uniform manner and separately from the main code, while detecting all errors.<ref name="exception_summary">{{Cite book|title = The C++ Programming Language|last = Stroustrup|first = Bjarne|publisher = Addison Wesley|year = 2013|isbn = 9780321563842|location = |pages = 345}}</ref> Should an error occur, an exception is thrown (raised), which is then caught by the nearest suitable exception handler. The exception causes the current scope to be exited, and also each outer scope (propagation) until a suitable handler is found, calling in turn the destructors of any objects in these exited scopes.<ref>{{Cite book|title = The C++ Programming Language|last = Stroustrup|first = Bjarne|publisher = Addison Wesley|year = 2013|isbn = 9780321563842|location = |pages = 363–365}}</ref> At the same time, an exception is presented as an object carrying the data about the detected problem.<ref>{{Cite book|title = The C++ Programming Language|last = Stroustrup|first = Bjarne|publisher = Addison Wesley|year = 2013|isbn = 9780321563842|location = |pages = 345, 363}}</ref>

The exception-causing code is placed inside a <syntaxhighlight lang="C++" inline>try</syntaxhighlight> block. The exceptions are handled in separate <syntaxhighlight lang="C++" inline>catch</syntaxhighlight> blocks (the handlers); each <syntaxhighlight lang="C++" inline>try</syntaxhighlight> block can have multiple exception handlers, as it is visible in the example below.<ref>{{Cite book|title = The C++ Programming Language|last = Stroustrup|first = Bjarne|publisher = Addison Wesley|year = 2013|isbn = 9780321563842|location = |pages = 344, 370}}</ref>

The exception-causing code is placed inside a <syntaxhighlight lang="C++" inline>try</syntaxhighlight> block. The exceptions are handled in separate <syntaxhighlight lang="C++" inline>catch</syntaxhighlight> blocks (the handlers); each <syntaxhighlight lang="C++" inline>try</syntaxhighlight> block can have multiple exception handlers, as it is visible in the example below.<ref>{{Cite book|title = The C++ Programming Language|last = Stroustrup|first = Bjarne|publisher = Addison Wesley|year = 2013|isbn = 9780321563842|location = |pages = 344, 370}}</ref>

<!--"#include <iostream.h> is deprecated"-->

<!--"#include <iostream.h> is deprecated"-->

#include <iostream>

#include <iostream>

#include <vector>

#include <vector>

     }

     }

}

}

It is also possible to raise exceptions purposefully, using the <syntaxhighlight lang="C++" inline>throw</syntaxhighlight> keyword; these exceptions are handled in the usual way. In some cases, exceptions cannot be used due to technical reasons. One such example is a critical component of an embedded system, where every operation must be guaranteed to complete within a specified amount of time. This cannot be determined with exceptions as no tools exist to determine the maximum time required for an exception to be handled.<ref>{{Cite book|title = The C++ Programming Language|last = Stroustrup|first = Bjarne|publisher = Addison Wesley|year = 2013|isbn = 9780321563842|location = |pages = 349}}</ref>

It is also possible to raise exceptions purposefully, using the <syntaxhighlight lang="C++" inline>throw</syntaxhighlight> keyword; these exceptions are handled in the usual way. In some cases, exceptions cannot be used due to technical reasons. One such example is a critical component of an embedded system, where every operation must be guaranteed to complete within a specified amount of time. This cannot be determined with exceptions as no tools exist to determine the maximum time required for an exception to be handled.<ref>{{Cite book|title = The C++ Programming Language|last = Stroustrup|first = Bjarne|publisher = Addison Wesley|year = 2013|isbn = 9780321563842|location = |pages = 349}}</ref>

== Standard library ==

== Standard library ==

A large part of the C++ library is based on the [[Standard Template Library]] (STL). Useful tools provided by the STL include [[container (data structure)|container]]s as the collections of objects (such as [[array data structure|vector]]s and [[linked list|lists]]), [[iterator]]s that provide array-like access to containers, and [[algorithm]]s that perform operations such as searching and sorting.

A large part of the C++ library is based on the [[Standard Template Library]] (STL). Useful tools provided by the STL include [[container (data structure)|container]]s as the collections of objects (such as [[array data structure|vector]]s and [[linked list|lists]]), [[iterator]]s that provide array-like access to containers, and [[algorithm]]s that perform operations such as searching and sorting.

Most C++ compilers, and all major ones, provide a standards-conforming implementation of the C++ standard library.

Most C++ compilers, and all major ones, provide a standards-conforming implementation of the C++ standard library.

== Compatibility ==

== Compatibility ==

=== With C ===

=== With C ===

{{Details|Compatibility of C and C++}}

{{Details|Compatibility of C and C++}}

== Criticism ==

== Criticism ==

Despite its widespread adoption, some notable programmers have criticized the C++ language, including [[Linus Torvalds]],<ref name=torvalds>{{cite mailing list |url=https://lwn.net/Articles/249460/ |title=Re: [RFC] Convert builin-mailinfo.c to use The Better String Library |date=6 September 2007 |accessdate=31 March 2015 }}</ref> [[Richard Stallman]],<ref>{{cite mailing list |url=http://harmful.cat-v.org/software/c++/rms |title=Re: Efforts to attract more users? |date=12 July 2010 |accessdate=31 March 2015 }}</ref> [[Joshua Bloch]], [[Ken Thompson]],<ref>{{cite web |url=https://www.drdobbs.com/open-source/interview-with-ken-thompson/229502480 |title=Dr. Dobb's: Interview with Ken Thompson |author=Andrew Binstock |date=18 May 2011 |accessdate=7 February 2014}}</ref><ref name="Seibel2009">{{cite book|author=Peter Seibel|title=Coders at Work: Reflections on the Craft of Programming|url=https://books.google.com/books?id=nneBa6-mWfgC&pg=PA475|date=16 September 2009|publisher=Apress|isbn=978-1-4302-1948-4|pages=475–476}}</ref><ref name="gigamonkeysWordpress">https://gigamonkeys.wordpress.com/2009/10/16/coders-c-plus-plus/</ref> and [[Donald Knuth]].<ref name="dobbsKnuth">https://www.drdobbs.com/architecture-and-design/an-interview-with-donald-knuth/228700500</ref><ref name="knuth1993">http://tex.loria.fr/litte/knuth-interview</ref>

Despite its widespread adoption, some notable programmers have criticized the C++ language, including [[Linus Torvalds]],<ref name=torvalds>{{cite mailing list |url=https://lwn.net/Articles/249460/ |title=Re: [RFC] Convert builin-mailinfo.c to use The Better String Library |date=6 September 2007 |accessdate=31 March 2015 }}</ref> [[Richard Stallman]],<ref>{{cite mailing list |url=http://harmful.cat-v.org/software/c++/rms |title=Re: Efforts to attract more users? |date=12 July 2010 |accessdate=31 March 2015 }}</ref> [[Joshua Bloch]], [[Ken Thompson]],<ref>{{cite web |url=https://www.drdobbs.com/open-source/interview-with-ken-thompson/229502480 |title=Dr. Dobb's: Interview with Ken Thompson |author=Andrew Binstock |date=18 May 2011 |accessdate=7 February 2014}}</ref><ref name="Seibel2009">{{cite book|author=Peter Seibel|title=Coders at Work: Reflections on the Craft of Programming|url=https://books.google.com/books?id=nneBa6-mWfgC&pg=PA475|date=16 September 2009|publisher=Apress|isbn=978-1-4302-1948-4|pages=475–476}}</ref><ref name="gigamonkeysWordpress">https://gigamonkeys.wordpress.com/2009/10/16/coders-c-plus-plus/</ref> and [[Donald Knuth]].<ref name="dobbsKnuth">https://www.drdobbs.com/architecture-and-design/an-interview-with-donald-knuth/228700500</ref><ref name="knuth1993">http://tex.loria.fr/litte/knuth-interview</ref>

[[Donald Knuth]] (1993, commenting on pre-standardized C++), who said of [[Edsger Dijkstra]] that "to think of programming in C++" "would make him physically ill":<ref name="dobbsKnuth" /><ref name="knuth1993" /> <blockquote> The problem that I have with them today is that... C++ is too complicated. At the moment, it's impossible for me to write portable code that I believe would work on lots of different systems, unless I avoid all exotic features. Whenever the C++ language designers had two competing ideas as to how they should solve some problem, they said "OK, we'll do them both". So the language is too baroque for my taste. </blockquote>

[[Donald Knuth]] (1993, commenting on pre-standardized C++), who said of [[Edsger Dijkstra]] that "to think of programming in C++" "would make him physically ill":<ref name="dobbsKnuth" /><ref name="knuth1993" /> <blockquote> The problem that I have with them today is that... C++ is too complicated. At the moment, it's impossible for me to write portable code that I believe would work on lots of different systems, unless I avoid all exotic features. Whenever the C++ language designers had two competing ideas as to how they should solve some problem, they said "OK, we'll do them both". So the language is too baroque for my taste. </blockquote>

Stroustrup campaigned for years and years and years, way beyond any sort of technical contributions he made to the language, to get it adopted and used. And he sort of ran all the standards committees with a whip and a chair. And he said “no” to no one. He put every feature in that language that ever existed. It wasn’t cleanly designed—it was just the union of everything that came along. And I think it suffered drastically from that. </blockquote>

Stroustrup campaigned for years and years and years, way beyond any sort of technical contributions he made to the language, to get it adopted and used. And he sort of ran all the standards committees with a whip and a chair. And he said “no” to no one. He put every feature in that language that ever existed. It wasn’t cleanly designed—it was just the union of everything that came along. And I think it suffered drastically from that. </blockquote>

Stroustrup himself comments that C++ semantics are much cleaner than its syntax: "within C++, there is a much smaller and cleaner language struggling to get out".<ref>http://www.stroustrup.com/bs_faq.html#really-say-that</ref>

Stroustrup himself comments that C++ semantics are much cleaner than its syntax: "within C++, there is a much smaller and cleaner language struggling to get out".<ref>http://www.stroustrup.com/bs_faq.html#really-say-that</ref>

== See also ==

== See also ==

* [[Comparison of programming languages]]

* [[Comparison of programming languages]]

* [[List of C++ compilers]]

* [[List of C++ compilers]]

* [[Outline of C++]]

* [[Outline of C++]]

* [[:Category:C++ libraries|C++ Libraries (category)]]

* [[:Category:C++ libraries|C++ Libraries (category)]]

== References ==

== References ==

== External links ==

== External links ==

* [http://www.open-std.org/jtc1/sc22/wg21/ JTC1/SC22/WG21]{{snd}} the ISO/IEC C++ Standard Working Group

* [http://www.open-std.org/jtc1/sc22/wg21/ JTC1/SC22/WG21]{{snd}} the ISO/IEC C++ Standard Working Group

* [https://isocpp.org/ Standard C++ Foundation]{{snd}} a non-profit organization that promotes the use and understanding of standard C++. Bjarne Stroustrup is a director of the organization.

* [https://isocpp.org/ Standard C++ Foundation]{{snd}} a non-profit organization that promotes the use and understanding of standard C++. Bjarne Stroustrup is a director of the organization.

[[Category:Algol programming language family]]

[[Category:Algol programming language family]]

[[Category:C++| ]]

[[Category:C++| ]]