tmp/tmpgcrpd1zp/{from.md → to.md}
RENAMED
|
@@ -8,21 +8,23 @@ subset provided by a freestanding implementation) and the C++ headers
|
|
| 8 |
for C library facilities ([[headers.cpp.c]]). It additionally exports
|
| 9 |
declarations in the global namespace for the storage allocation and
|
| 10 |
deallocation functions that are provided by `<new>`.
|
| 11 |
|
| 12 |
The named module `std.compat` exports the same declarations as the named
|
| 13 |
-
module `std`, and additionally exports
|
| 14 |
-
|
| 15 |
-
|
| 16 |
-
|
| 17 |
-
|
|
|
|
|
|
|
| 18 |
|
| 19 |
It is unspecified to which module a declaration in the standard library
|
| 20 |
is attached.
|
| 21 |
|
| 22 |
-
[*Note 1*:
|
| 23 |
-
`
|
| 24 |
[[basic.link]]. — *end note*]
|
| 25 |
|
| 26 |
*Recommended practice:* Implementations should ensure such attachments
|
| 27 |
do not preclude further evolution or decomposition of the standard
|
| 28 |
library modules.
|
|
|
|
| 8 |
for C library facilities ([[headers.cpp.c]]). It additionally exports
|
| 9 |
declarations in the global namespace for the storage allocation and
|
| 10 |
deallocation functions that are provided by `<new>`.
|
| 11 |
|
| 12 |
The named module `std.compat` exports the same declarations as the named
|
| 13 |
+
module `std`, and additionally exports
|
| 14 |
+
|
| 15 |
+
- declarations in the global namespace corresponding to the declarations
|
| 16 |
+
in namespace `std` that are provided by the C++ headers for C library
|
| 17 |
+
facilities ([[headers.cpp.c]]), except the explicitly excluded
|
| 18 |
+
declarations described in [[support.c.headers.other]] and
|
| 19 |
+
- declarations provided by the headers `<stdbit.h>` and `<stdckdint.h>`.
|
| 20 |
|
| 21 |
It is unspecified to which module a declaration in the standard library
|
| 22 |
is attached.
|
| 23 |
|
| 24 |
+
[*Note 1*: Conforming implementations ensure that mixing `#include` and
|
| 25 |
+
`import` does not result in conflicting attachments
|
| 26 |
[[basic.link]]. — *end note*]
|
| 27 |
|
| 28 |
*Recommended practice:* Implementations should ensure such attachments
|
| 29 |
do not preclude further evolution or decomposition of the standard
|
| 30 |
library modules.
|