15 Library introduction [library]

15.5 Library-wide requirements [requirements]

15.5.1 Library contents and organization [organization]

1
#
[contents] describes the entities and macros defined in the C++ standard library.
[headers] lists the standard library headers and some constraints on those headers.
[compliance] lists requirements for a freestanding implementation of the C++ standard library.

15.5.1.1 Library contents [contents]

1
#
The C++ standard library provides definitions for the entities and macros described in the synopses of the C++ standard library headers ([headers]).
2
#
All library entities except operator new and operator delete are defined within the namespace std or namespaces nested within namespace std.167
It is unspecified whether names declared in a specific namespace are declared directly in that namespace or in an inline namespace inside that namespace.168
3
#
Whenever a name x defined in the standard library is mentioned, the name x is assumed to be fully qualified as ​::​std​::​x, unless explicitly described otherwise.
For example, if the Effects: element for library function F is described as calling library function G, the function ​::​std​::​G is meant.
167)
The C standard library headers ([depr.c.headers]) also define names within the global namespace, while the C++ headers for C library facilities ([headers]) may also define names within the global namespace.
168)
This gives implementers freedom to use inline namespaces to support multiple configurations of the library.

15.5.1.2 Headers [headers]

1
#
Each element of the C++ standard library is declared or defined (as appropriate) in a header.169
2
#
The C++ standard library provides the C++ library headers, shown in Table 18.
Table 18 — C++ library headers
[t]l <algorithm>
<any>
<array>
<atomic>
<bit>
<bitset>
<charconv>
<chrono>
<codecvt>
<compare>
<complex>
<concepts>
<condition_­variable>
<contract>
<deque>
<exception>
<execution>
<filesystem>
<forward_­list>
<fstream>
<functional>
<future>
<initializer_­list>
<iomanip>
<ios>
<iosfwd>
<iostream>
<istream>
<iterator>
<limits>
<list>
<locale>
<map>
<memory>
<memory_­resource>
<mutex>
<new>
<numeric>
<optional>
<ostream>
<queue>
<random>
<ratio>
<regex>
<scoped_­allocator>
<set>
<shared_­mutex>
<span>
<sstream>
<stack>
<stdexcept>
<streambuf>
<string>
<string_­view>
<strstream>
<syncstream>
<system_­error>
<thread>
<tuple>
<typeindex>
<typeinfo>
<type_­traits>
<unordered_­map>
<unordered_­set>
<utility>
<valarray>
<variant>
<vector>
<version>
3
#
The facilities of the C standard library are provided in the additional headers shown in Table 19.170
Table 19 — C++ headers for C library facilities
[t]l <cassert>
<cctype>
<cerrno>
<cfenv>
<cfloat>
<cinttypes>
<climits>
<clocale>
<cmath>
<csetjmp>
<csignal>
<cstdarg>
<cstddef>
<cstdint>
<cstdio>
<cstdlib>
<cstring>
<ctime>
<cuchar>
<cwchar>
<cwctype>
4
#
Except as noted in [library] through [thread] and [depr], the contents of each header cname is the same as that of the corresponding header name.h as specified in the C standard library.
In the C++ standard library, however, the declarations (except for names which are defined as macros in C) are within namespace scope of the namespace std.
It is unspecified whether these names (including any overloads added in [language.support] through [thread] and [depr]) are first declared within the global namespace scope and are then injected into namespace std by explicit using-declarations.
5
#
Names which are defined as macros in C shall be defined as macros in the C++ standard library, even if C grants license for implementation as functions.
[ Note
:
The names defined as macros in C include the following: assert, offsetof, setjmp, va_­arg, va_­end, and va_­start.
— end note
 ]
6
#
Names that are defined as functions in C shall be defined as functions in the C++ standard library.171
7
#
Identifiers that are keywords or operators in C++ shall not be defined as macros in C++ standard library headers.172
8
#
[depr.c.headers], C standard library headers, describes the effects of using the name.h (C header) form in a C++ program.173
9
#
Annex K of the C standard describes a large number of functions, with associated types and macros, which “promote safer, more secure programming” than many of the traditional C library functions.
The names of the functions have a suffix of _­s; most of them provide the same service as the C library function with the unsuffixed name, but generally take an additional argument whose value is the size of the result array.
If any C++ header is included, it is implementation-defined whether any of these names is declared in the global namespace.
(None of them is declared in namespace std.)
10
#
Table 20 lists the Annex K names that may be declared in some header.
These names are also subject to the restrictions of [macro.names].
Table 20 — C standard Annex K names
[t]l abort_­handler_­s
asctime_­s
bsearch_­s
constraint_­handler_­t
ctime_­s
errno_­t
fopen_­s
fprintf_­s
freopen_­s
fscanf_­s
fwprintf_­s
fwscanf_­s
getenv_­s
gets_­s
gmtime_­s
ignore_­handler_­s
localtime_­s
L_­tmpnam_­s
mbsrtowcs_­s
mbstowcs_­s
memcpy_­s
memmove_­s
memset_­s
printf_­s
qsort_­s
RSIZE_­MAX
rsize_­t
scanf_­s
set_­constraint_­handler_­s
snprintf_­s
snwprintf_­s
sprintf_­s
sscanf_­s
strcat_­s
strcpy_­s
strerrorlen_­s
strerror_­s
strlen_­s
strncat_­s
strncpy_­s
strtok_­s
swprintf_­s
swscanf_­s
tmpfile_­s
TMP_­MAX_­S
tmpnam_­s
vfprintf_­s
vfscanf_­s
vfwprintf_­s
vfwscanf_­s
vprintf_­s
vscanf_­s
vsnprintf_­s
vsnwprintf_­s
vsprintf_­s
vsscanf_­s
vswprintf_­s
vswscanf_­s
vwprintf_­s
vwscanf_­s
wcrtomb_­s
wcscat_­s
wcscpy_­s
wcsncat_­s
wcsncpy_­s
wcsnlen_­s
wcsrtombs_­s
wcstok_­s
wcstombs_­s
wctomb_­s
wmemcpy_­s
wmemmove_­s
wprintf_­s
wscanf_­s
169)
A header is not necessarily a source file, nor are the sequences delimited by < and > in header names necessarily valid source file names ([cpp.include]).
170)
It is intentional that there is no C++ header for any of these C headers: <stdatomic.h>, <stdnoreturn.h>, <threads.h>.
171)
This disallows the practice, allowed in C, of providing a masking macro in addition to the function prototype.
The only way to achieve equivalent inline behavior in C++ is to provide a definition as an extern inline function.
172)
In particular, including the standard header <iso646.h> has no effect.
173)
The ".h" headers dump all their names into the global namespace, whereas the newer forms keep their names in namespace std.
Therefore, the newer forms are the preferred forms for all uses except for C++ programs which are intended to be strictly compatible with C.

15.5.1.3 Freestanding implementations [compliance]

1
#
Two kinds of implementations are defined: hosted and freestanding ([intro.compliance]).
For a hosted implementation, this document describes the set of available headers.
2
#
A freestanding implementation has an implementation-defined set of headers.
This set shall include at least the headers shown in Table 21.
Table 21 — C++ headers for freestanding implementations
Subclause
Header(s)
Types
<cstddef>
Implementation properties
<cfloat> <limits> <climits> <version>
Integer types
<cstdint>
Start and termination
<cstdlib>
Dynamic memory management
<new>
Type identification
<typeinfo>
Exception handling
<exception>
Initializer lists
<initializer_­list>
Other runtime support
<cstdarg>
Type traits
<type_­traits>
Bit manipulation
<bit>
Atomics
<atomic>
3
#
The supplied version of the header <cstdlib> shall declare at least the functions abort, atexit, at_­quick_­exit, exit, and quick_­exit ([support.start.term]).
The other headers listed in this table shall meet the same requirements as for a hosted implementation.