Subcategories 2
Sites 26
A number of compilers allow the programmer to suppress the implicit instantiation of templates by prefixing an explicit instantiation directive with the extern keyword. This document proposes specific semantics for this feature.
This note explains the reasons for the removal of "concepts," briefly outlines the controversy and fears that caused the committee to decide the way it did, gives references for people who would like to explore "concepts," and points out that (despite enthusiastic rumors to the contrary) "the sky is not falling" on C++.
Concepts introduce a type system for templates that makes templates easier to use and easier to write. By checking the requirements that templates place on their parameters prior to template instantiation, concepts can eliminate the spectacularly poor error messages produced by today’s template libraries, making them easier to use.
[PDF]
Suggests extending C++ with a decltype operator for querying the type of an expression. Also suggests a new function declaration syntax, which allows one to place the return type expression syntactically after the list of function parameters.
[PDF]
October 1997 working paper of the proposed standard.
A subset of C++ intended for embedded systems programming. It is defined by an industry consortium, the Embedded C++ Technical Committee.
Buy a PDF version of the official C++ programming language standard from the ANSI Electronic Standards Store.
The international standardization working group for the programming language C++.
Contains links to the latest library TR1 (technical report 1) draft as well as to the most relevant standardization documents that motivate and explain TR1 functionality.
Understanding compiler rules better equips you to interpret messages the compiler sends you.
Discusses the addition of almost all of TR1 to the new C++ Standard.
Proposes integrating a memory model suitable for multithreaded execution in the C++ Standard. On top of that model, a standard threading library is proposed.
[PDF]
This paper proposes a module mechanism (somewhat similar to that of Modula-2) with three primary goals: significantly improve build times of large projects, enable a better separation between interface and implementation, and provide a viable transition path for existing libraries.
[PDF]
Introduces people and groups involved in the C++ standardization process.
Takes a closer look at one of the proposed facilities - smart pointers, which were discussed again at the April 2002 standards meeting.
Presents a survey of the first batch of suggested library extensions that were considered at the October 2001 WG21/J16 meeting in Redmond.
An update on the most recent C++ standards meeting, and why things are (finally) heating up.
Presents an overview of the proposed typedef templates.
This proposal describes a small assertion sub-language that unifies compile-time and run-time assertions. The benefits are among others a higher degree of self-documenting source code, better design tools, and easier debugging and testing.
The C++ language currently supports two facilities for testing software assertions: the assert macro and the #error preprocessor directive. Neither of these facilities is appropriate for use in template libraries.
Explains ways to allow >> to be treated as two closing angle brackets, as well as to discuss the resulting issues. A specific option is proposed along with wording that would implement the proposal in the current working paper.
Small number of changes which allow safely encapsulating pointer operations, via "smart pointers" and version of STL with subscript and iterator checks. For next generation of C++ revision cycle; refined with online C++ community.
Discusses three questions related to the removal of concepts: what led to the failure of Concepts, how will the removal of Concepts affect C++0x, and will Concepts make a comeback in the near future?
(July 17, 2009)
The C++ standardization committee is hard at work standardizing threads for the next version of C++. Some members recently met to discuss the issues.
(October 17, 2006)
Offers a sneak peek at the next version of standard C++. It briefly outlines the guiding principles of the work on C++0x, presents a few examples of likely language extensions, and lists some proposed new standard libraries.
(January 02, 2006)
This article appeared in C/C++ Users Journal, 20(1).
(January 01, 2002)
Buy a PDF version of the official C++ programming language standard from the ANSI Electronic Standards Store.
Understanding compiler rules better equips you to interpret messages the compiler sends you.
Presents an overview of the proposed typedef templates.
This note explains the reasons for the removal of "concepts," briefly outlines the controversy and fears that caused the committee to decide the way it did, gives references for people who would like to explore "concepts," and points out that (despite enthusiastic rumors to the contrary) "the sky is not falling" on C++.
An update on the most recent C++ standards meeting, and why things are (finally) heating up.
Discusses the addition of almost all of TR1 to the new C++ Standard.
Introduces people and groups involved in the C++ standardization process.
Takes a closer look at one of the proposed facilities - smart pointers, which were discussed again at the April 2002 standards meeting.
Presents a survey of the first batch of suggested library extensions that were considered at the October 2001 WG21/J16 meeting in Redmond.
Small number of changes which allow safely encapsulating pointer operations, via "smart pointers" and version of STL with subscript and iterator checks. For next generation of C++ revision cycle; refined with online C++ community.
Concepts introduce a type system for templates that makes templates easier to use and easier to write. By checking the requirements that templates place on their parameters prior to template instantiation, concepts can eliminate the spectacularly poor error messages produced by today’s template libraries, making them easier to use.
[PDF]
A subset of C++ intended for embedded systems programming. It is defined by an industry consortium, the Embedded C++ Technical Committee.
A number of compilers allow the programmer to suppress the implicit instantiation of templates by prefixing an explicit instantiation directive with the extern keyword. This document proposes specific semantics for this feature.
October 1997 working paper of the proposed standard.
Explains ways to allow >> to be treated as two closing angle brackets, as well as to discuss the resulting issues. A specific option is proposed along with wording that would implement the proposal in the current working paper.
This paper proposes a module mechanism (somewhat similar to that of Modula-2) with three primary goals: significantly improve build times of large projects, enable a better separation between interface and implementation, and provide a viable transition path for existing libraries.
[PDF]
The C++ language currently supports two facilities for testing software assertions: the assert macro and the #error preprocessor directive. Neither of these facilities is appropriate for use in template libraries.
Suggests extending C++ with a decltype operator for querying the type of an expression. Also suggests a new function declaration syntax, which allows one to place the return type expression syntactically after the list of function parameters.
[PDF]
This proposal describes a small assertion sub-language that unifies compile-time and run-time assertions. The benefits are among others a higher degree of self-documenting source code, better design tools, and easier debugging and testing.
Contains links to the latest library TR1 (technical report 1) draft as well as to the most relevant standardization documents that motivate and explain TR1 functionality.
The international standardization working group for the programming language C++.
Proposes integrating a memory model suitable for multithreaded execution in the C++ Standard. On top of that model, a standard threading library is proposed.
[PDF]
Discusses three questions related to the removal of concepts: what led to the failure of Concepts, how will the removal of Concepts affect C++0x, and will Concepts make a comeback in the near future?
(July 17, 2009)
The C++ standardization committee is hard at work standardizing threads for the next version of C++. Some members recently met to discuss the issues.
(October 17, 2006)
Offers a sneak peek at the next version of standard C++. It briefly outlines the guiding principles of the work on C++0x, presents a few examples of likely language extensions, and lists some proposed new standard libraries.
(January 02, 2006)
This article appeared in C/C++ Users Journal, 20(1).
(January 01, 2002)
