This page is a snapshot from the LWG issues list, see the Library Active Issues List for more information and the meaning of NAD status.
Section: 16.4.2.3 [headers] Status: NAD Submitter: Alisdair Meredith Opened: 2009-03-11 Last modified: 2016-01-28
Priority: Not Prioritized
View all other issues in [headers].
View all issues with NAD status.
Discussion:
Addresses UK-170 [CD1]
One of goals of C++0x is to make language easier to teach and for 'incidental' programmers. The fine-grained headers of the C++ library are valuable in large scale systems for managing dependencies and optimising build times, but overcomplicated for simple development and tutorials. Add additional headers to support the whole library through a single include statement.
[ Batavia (2009-05): ]
We do not all agree that this is an issue, but we agree that if it needs solving this is the right way to do it. Move to Tentatively Ready.
[ 2009-07-06 Beman notes: ]
This issue adds a header
<std>
.There is a paper to be looked at, N2905 Aggregation headers, that adds a header
<std-all>
that is the same thing except it excludes deprecated headers. N2905 also proposes a second aggregation header.Seems like this issue should be held in abeyance until the LWG has had a chance to look at N2905.
[ 2009-07-06 Howard: I've pulled this issue back to Review. ]
[ 2009-07 Frankfurt ]
No consensus for change.
Proposed resolution:
Insert a new paragraph in 16.4.2.3 [headers] between p4 and p5
An additional header
<std>
shall have the effect of supplying the entire standard library. [Note: for example, it might be implemented as a file with an#include
statement for each of the headers listed in tables 13 and 14. -- end note]