tmp/tmp0t64sn9w/{from.md → to.md}
RENAMED
|
@@ -0,0 +1,20 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
### Other C headers <a id="depr.c.headers.other">[[depr.c.headers.other]]</a>
|
| 2 |
+
|
| 3 |
+
Every C header other than , , , , and , each of which has a name of the
|
| 4 |
+
form `<name.h>`, behaves as if each name placed in the standard library
|
| 5 |
+
namespace by the corresponding `<cname>` header is placed within the
|
| 6 |
+
global namespace scope, except for the functions described in
|
| 7 |
+
[[sf.cmath]], the declaration of `std::byte` [[cstddef.syn]], and the
|
| 8 |
+
functions and function templates described in [[support.types.byteops]].
|
| 9 |
+
It is unspecified whether these names are first declared or defined
|
| 10 |
+
within namespace scope [[basic.scope.namespace]] of the namespace `std`
|
| 11 |
+
and are then injected into the global namespace scope by explicit
|
| 12 |
+
*using-declaration*s [[namespace.udecl]].
|
| 13 |
+
|
| 14 |
+
[*Example 1*: The header `<cstdlib>` assuredly provides its
|
| 15 |
+
declarations and definitions within the namespace `std`. It may also
|
| 16 |
+
provide these names within the global namespace. The header `<stdlib.h>`
|
| 17 |
+
assuredly provides the same declarations and definitions within the
|
| 18 |
+
global namespace, much as in the C Standard. It may also provide these
|
| 19 |
+
names within the namespace `std`. — *end example*]
|
| 20 |
+
|