[cpp] - C++23 → Trunk

Files changed (1) hide show

tmp/tmpkh_s32k7/{from.md → to.md} +749 -191

tmp/tmpkh_s32k7/{from.md → to.md} RENAMED Viewed

@@ -39,10 +39,11 @@ group-part:
 ``` bnf
 control-line:
     '# include' pp-tokens new-line
     pp-import
     '# define ' identifier replacement-list new-line
     '# define ' identifier lparen identifier-listₒₚₜ ')' replacement-list new-line
     '# define ' identifier lparen '... )' replacement-list new-line
     '# define ' identifier lparen identifier-list ', ... )' replacement-list new-line
     '# undef ' identifier new-line
@@ -65,12 +66,11 @@ if-group:
     '# ifndef ' identifier new-line groupₒₚₜ
 ```
 ``` bnf
 elif-groups:
-    elif-group
-    elif-groups elif-group
 ```
 ``` bnf
 elif-group:
     '# elif ' constant-expression new-line groupₒₚₜ
@@ -114,39 +114,86 @@ replacement-list:
     pp-tokensₒₚₜ
 ```
 ``` bnf
 pp-tokens:
-    preprocessing-token
-    pp-tokens preprocessing-token
 ```
 ``` bnf
 new-line:
     the new-line character
 ```
 A *preprocessing directive* consists of a sequence of preprocessing
 tokens that satisfies the following constraints: At the start of
-translation phase 4, the first token in the sequence, referred to as a
-*directive-introducing token*, begins with the first character in the
-source file (optionally after whitespace containing no new-line
-characters) or follows whitespace containing at least one new-line
-character, and is
 - a `#` preprocessing token, or
 - an `import` preprocessing token immediately followed on the same
-  logical line by a *header-name*, `<`, *identifier*, *string-literal*,
-  or `:` preprocessing token, or
 - a `module` preprocessing token immediately followed on the same
-  logical line by an *identifier*, `:`, or `;` preprocessing token, or
 - an `export` preprocessing token immediately followed on the same
-  logical line by one of the two preceding forms.
-The last token in the sequence is the first token within the sequence
-that is immediately followed by whitespace containing a new-line
-character.[^1]
 [*Note 1*: A new-line character ends the preprocessing directive even
 if it occurs within what would otherwise be an invocation of a
 function-like macro. — *end note*]
@@ -176,15 +223,38 @@ import ->               // not a preprocessing directive
 ```
 — *end example*]
 A sequence of preprocessing tokens is only a *text-line* if it does not
-begin with a directive-introducing token. A sequence of preprocessing
-tokens is only a *conditionally-supported-directive* if it does not
-begin with any of the directive names appearing after a `#` in the
-syntax. A *conditionally-supported-directive* is conditionally-supported
-with *implementation-defined* semantics.
 At the start of phase 4 of translation, the *group* of a
 *pp-global-module-fragment* shall contain neither a *text-line* nor a
 *pp-import*.
@@ -193,24 +263,18 @@ relaxed to allow any sequence of preprocessing tokens to occur between
 the directive name and the following new-line character.
 The only whitespace characters that shall appear between preprocessing
 tokens within a preprocessing directive (from just after the
 directive-introducing token through just before the terminating new-line
-character) are space and horizontal-tab (including spaces that have
-replaced comments or possibly other whitespace characters in translation
-phase 3).
-The implementation can process and skip sections of source files
-conditionally, include other source files, import macros from header
-units, and replace macros. These capabilities are called
-*preprocessing*, because conceptually they occur before translation of
-the resulting translation unit.
 The preprocessing tokens within a preprocessing directive are not
 subject to macro expansion unless otherwise stated.
-[*Example 2*:
 In:
 ``` cpp
 #define EMPTY
@@ -237,12 +301,11 @@ h-preprocessing-token:
     any *preprocessing-token* other than '>'
 ```
 ``` bnf
 h-pp-tokens:
-    h-preprocessing-token
-    h-pp-tokens h-preprocessing-token
 ```
 ``` bnf
 header-name-tokens:
     string-literal
@@ -253,79 +316,104 @@ header-name-tokens:
 has-include-expression:
     '__has_include' '(' header-name ')'
     '__has_include' '(' header-name-tokens ')'
 ```
 ``` bnf
 has-attribute-expression:
     '__has_cpp_attribute (' pp-tokens ')'
 ```
 The expression that controls conditional inclusion shall be an integral
 constant expression except that identifiers (including those lexically
 identical to keywords) are interpreted as described below[^2]
-and it may contain zero or more *defined-macro-expression*s and/or
-*has-include-expression*s and/or *has-attribute-expression*s as unary
-operator expressions.
 A *defined-macro-expression* evaluates to `1` if the identifier is
 currently defined as a macro name (that is, if it is predefined or if it
 has one or more active macro definitions [[cpp.import]], for example
 because it has been the subject of a `#define` preprocessing directive
 without an intervening `#undef` directive with the same subject
 identifier), `0` if it is not.
-The second form of *has-include-expression* is considered only if the
-first form does not match, in which case the preprocessing tokens are
-processed just as in normal text.
 The header or source file identified by the parenthesized preprocessing
 token sequence in each contained *has-include-expression* is searched
-for as if that preprocessing token sequence were the *pp-tokens* in a
 `#include` directive, except that no further macro expansion is
-performed. If such a directive would not satisfy the syntactic
-requirements of a `#include` directive, the program is ill-formed. The
 *has-include-expression* evaluates to `1` if the search for the source
 file succeeds, and to `0` if the search fails.
 Each *has-attribute-expression* is replaced by a non-zero *pp-number*
 matching the form of an *integer-literal* if the implementation supports
 an attribute with the name specified by interpreting the *pp-tokens*,
 after macro expansion, as an *attribute-token*, and by `0` otherwise.
 The program is ill-formed if the *pp-tokens* do not match the form of an
 *attribute-token*.
-For an attribute specified in this document, the value of the
-*has-attribute-expression* is given by [[cpp.cond.ha]]. For other
-attributes recognized by the implementation, the value is
 *implementation-defined*.
-[*Note 1*: It is expected that the availability of an attribute can be
 detected by any non-zero result. — *end note*]
 **Table: __has_cpp_attribute values** <a id="cpp.cond.ha">[cpp.cond.ha]</a>
 | Attribute           | Value     |
-| -------------------- | --------- |
 | `assume`            | `202207L` |
-| `carries_dependency` | `200809L` |
 | `deprecated`        | `201309L` |
 | `fallthrough`       | `201603L` |
 | `likely`            | `201803L` |
 | `maybe_unused`      | `201603L` |
 | `no_unique_address` | `201803L` |
 | `nodiscard`         | `201907L` |
 | `noreturn`          | `200809L` |
 | `unlikely`          | `201803L` |
 The `#ifdef`, `#ifndef`, `#elifdef`, and `#elifndef` directives, and the
-`defined` conditional inclusion operator, shall treat `__has_include`
-and `__has_cpp_attribute` as if they were the names of defined macros.
-The identifiers `__has_include` and `__has_cpp_attribute` shall not
-appear in any context not mentioned in this subclause.
 Each preprocessing token that remains (in the list of preprocessing
 tokens that will become the controlling expression) after all macro
 replacements have occurred shall be in the lexical form of a token
 [[lex.token]].
@@ -340,44 +428,50 @@ Preprocessing directives of the forms
 check whether the controlling constant expression evaluates to nonzero.
 Prior to evaluation, macro invocations in the list of preprocessing
 tokens that will become the controlling constant expression are replaced
 (except for those macro names modified by the `defined` unary operator),
-just as in normal text. If the token `defined` is generated as a result
-of this replacement process or use of the `defined` unary operator does
-not match one of the two specified forms prior to macro replacement, the
-behavior is undefined.
 After all replacements due to macro expansion and evaluations of
-*defined-macro-expression*s, *has-include-expression*s, and
-*has-attribute-expression*s have been performed, all remaining
-identifiers and keywords, except for `true` and `false`, are replaced
-with the *pp-number* `0`, and then each preprocessing token is converted
-into a token.
-[*Note 2*: An alternative token [[lex.digraph]] is not an identifier,
 even when its spelling consists entirely of letters and underscores.
 Therefore it is not subject to this replacement. — *end note*]
 The resulting tokens comprise the controlling constant expression which
 is evaluated according to the rules of  [[expr.const]] using arithmetic
 that has at least the ranges specified in  [[support.limits]]. For the
 purposes of this token conversion and evaluation all signed and unsigned
 integer types act as if they have the same representation as,
 respectively, `intmax_t` or `uintmax_t` [[cstdint.syn]].
-[*Note 3*: Thus on an implementation where
 `std::numeric_limits<int>::max()` is `0x7FFF` and
 `std::numeric_limits<unsigned int>::max()` is `0xFFFF`, the integer
 literal `0x8000` is signed and positive within a `#if` expression even
 though it is unsigned in translation phase 7
 [[lex.phases]]. — *end note*]
 This includes interpreting *character-literal*s according to the rules
 in [[lex.ccon]].
-[*Note 4*: The associated character encodings of literals are the same
 in `#if` and `#elif` directives and in any expression. — *end note*]
 Each subexpression with type `bool` is subjected to integral promotion
 before processing continues.
@@ -395,20 +489,20 @@ name. Their conditions are equivalent to `#if` `defined` *identifier*,
 `#if` `!defined` *identifier*, `#elif` `defined` *identifier*, and
 `#elif` `!defined` *identifier*, respectively.
 Each directive’s condition is checked in order. If it evaluates to false
 (zero), the group that it controls is skipped: directives are processed
-only through the name that determines the directive in order to keep
-track of the level of nested conditionals; the rest of the directives’
-preprocessing tokens are ignored, as are the other preprocessing tokens
-in the group. Only the first group whose control condition evaluates to
-true (nonzero) is processed; any following groups are skipped and their
-controlling directives are processed as if they were in a group that is
-skipped. If none of the conditions evaluates to true, and there is a
-`#else` directive, the group controlled by the `#else` is processed;
-lacking a `#else` directive, all the groups until the `#endif` are
-skipped.[^3]
 [*Example 1*:
 This demonstrates a way to include a library `optional` facility only if
 it is available:
@@ -449,61 +543,80 @@ ATTR_DEPRECATED("This function is deprecated") void anvil();
 — *end example*]
 ## Source file inclusion <a id="cpp.include">[[cpp.include]]</a>
-A `#include` directive shall identify a header or source file that can
-be processed by the implementation.
-A preprocessing directive of the form
-``` bnf
-'# include <' h-char-sequence '>' new-line
-```
-searches a sequence of *implementation-defined* places for a header
-identified uniquely by the specified sequence between the `<` and `>`
-delimiters, and causes the replacement of that directive by the entire
-contents of the header. How the places are specified or the header
-identified is *implementation-defined*.
 A preprocessing directive of the form
 ``` bnf
-'# include "' q-char-sequence '"' new-line
 ```
 causes the replacement of that directive by the entire contents of the
-source file identified by the specified sequence between the `"`
-delimiters. The named source file is searched for in an
-*implementation-defined* manner. If this search is not supported, or if
-the search fails, the directive is reprocessed as if it read
 ``` bnf
-'# include <' h-char-sequence '>' new-line
 ```
-with the identical contained sequence (including `>` characters, if any)
-from the original directive.
 A preprocessing directive of the form
 ``` bnf
 '# include' pp-tokens new-line
 ```
-(that does not match one of the two previous forms) is permitted. The
-preprocessing tokens after `include` in the directive are processed just
-as in normal text (i.e., each identifier currently defined as a macro
-name is replaced by its replacement list of preprocessing tokens). If
-the directive resulting after all replacements does not match one of the
-two previous forms, the behavior is undefined.[^4]
-The method by which a sequence of preprocessing tokens between a `<` and
-a `>` preprocessing token pair or a pair of `"` characters is combined
-into a single header name preprocessing token is
-*implementation-defined*.
 The implementation shall provide unique mappings for sequences
 consisting of one or more *nondigit*s or *digit*s [[lex.name]] followed
 by a period (`.`) and a single *nondigit*. The first character shall not
 be a *digit*. The implementation may ignore distinctions of alphabetical
@@ -517,14 +630,14 @@ If the header identified by the *header-name* denotes an importable
 header [[module.import]], it is *implementation-defined* whether the
 `#include` preprocessing directive is instead replaced by an `import`
 directive [[cpp.import]] of the form
 ``` bnf
-'import' header-name ';' new-line
 ```
-[*Note 1*:
 An implementation can provide a mechanism for making arbitrary source
 files available to the `< >` search. However, using the `< >` form for
 headers provided with the implementation and the `" "` form for sources
 outside the control of the implementation achieves wider portability.
@@ -554,20 +667,418 @@ This illustrates macro-replaced `#include` directives:
 #include INCFILE
 ```
 — *end example*]
 ## Module directive <a id="cpp.module">[[cpp.module]]</a>
 ``` bnf
 pp-module:
     exportₒₚₜ module pp-tokensₒₚₜ ';' new-line
 ```
 A *pp-module* shall not appear in a context where `module` or (if it is
-the first token of the *pp-module*) `export` is an identifier defined as
-an object-like macro.
 Any preprocessing tokens after the `module` preprocessing token in the
 `module` directive are processed just as in normal text.
 [*Note 1*: Each identifier currently defined as a macro name is
@@ -588,12 +1099,12 @@ pp-import:
     exportₒₚₜ import header-name-tokens pp-tokensₒₚₜ ';' new-line
     exportₒₚₜ import pp-tokens ';' new-line
 ```
 A *pp-import* shall not appear in a context where `import` or (if it is
-the first token of the *pp-import*) `export` is an identifier defined as
-an object-like macro.
 The preprocessing tokens after the `import` preprocessing token in the
 `import` *control-line* are processed just as in normal text (i.e., each
 identifier currently defined as a macro name is replaced by its
 replacement list of preprocessing tokens).
@@ -654,11 +1165,11 @@ translation unit and at most one point of undefinition, as follows:
   unit is the first point at which a `#undef` directive naming the macro
   occurs after its point of definition, or the first point of macro
   import of a header unit containing a point of undefinition for the
   macro definition, whichever (if any) occurs first.
-A macro directive is *active* at a source location if it has a point of
 definition in that translation unit preceding the location, and does not
 have a point of undefinition in that translation unit preceding the
 location.
 If a macro would be replaced or redefined, and multiple macro
@@ -791,10 +1302,16 @@ The identifier immediately following the `define` is called the *macro
 name*. There is one name space for macro names. Any whitespace
 characters preceding or following the replacement list of preprocessing
 tokens are not considered part of the replacement list for either form
 of macro.
 If a `#` preprocessing token, followed by an identifier, occurs
 lexically at the point at which a preprocessing directive can begin, the
 identifier is not subject to macro replacement.
 A preprocessing directive of the form
@@ -802,17 +1319,17 @@ A preprocessing directive of the form
 ``` bnf
 '# define' identifier replacement-list new-line
 ```
 defines an *object-like macro* that causes each subsequent instance of
-the macro name[^5]
 to be replaced by the replacement list of preprocessing tokens that
-constitute the remainder of the directive.[^6]
 The replacement list is then rescanned for more macro names as specified
-below.
 [*Example 2*:
 The simplest use of this facility is to define a “manifest constant”, as
 in
@@ -848,13 +1365,13 @@ The sequence of preprocessing tokens bounded by the outside-most
 matching parentheses forms the list of arguments for the function-like
 macro. The individual arguments within the list are separated by comma
 preprocessing tokens, but comma preprocessing tokens between matching
 inner parentheses do not separate arguments. If there are sequences of
 preprocessing tokens within the list of arguments that would otherwise
-act as preprocessing directives,[^7]
-the behavior is undefined.
 [*Example 3*:
 The following defines a function-like macro whose value is the maximum
 of its arguments. It has the disadvantages of evaluating one or the
@@ -888,22 +1405,22 @@ va-opt-replacement:
 After the arguments for the invocation of a function-like macro have
 been identified, argument substitution takes place. For each parameter
 in the replacement list that is neither preceded by a `#` or `##`
 preprocessing token nor followed by a `##` preprocessing token, the
-preprocessing tokens naming the parameter are replaced by a token
-sequence determined as follows:
 - If the parameter is of the form *va-opt-replacement*, the replacement
   preprocessing tokens are the preprocessing token sequence for the
   corresponding argument, as specified below.
 - Otherwise, the replacement preprocessing tokens are the preprocessing
   tokens of corresponding argument after all macros contained therein
   have been expanded. The argument’s preprocessing tokens are completely
   macro replaced before being substituted as if they formed the rest of
-  the preprocessing file with no other preprocessing tokens being
-  available.
 [*Example 1*:
 ``` cpp
 #define LPAREN() (
@@ -1019,17 +1536,21 @@ argument’s preprocessing tokens becomes a single space character in the
 character string literal. Whitespace before the first preprocessing
 token and after the last preprocessing token comprising the stringizing
 argument is deleted. Otherwise, the original spelling of each
 preprocessing token in the stringizing argument is retained in the
 character string literal, except for special handling for producing the
-spelling of *string-literal*s and *character-literal*s: a `\` character
-is inserted before each `"` and `\` character of a *character-literal*
-or *string-literal* (including the delimiting `"` characters). If the
-replacement that results is not a valid character string literal, the
-behavior is undefined. The character string literal corresponding to an
-empty stringizing argument is `""`. The order of evaluation of `#` and
-`##` operators is unspecified.
 ### The `##` operator <a id="cpp.concat">[[cpp.concat]]</a>
 A `##` preprocessing token shall not occur at the beginning or at the
 end of a replacement list for either form of macro definition.
@@ -1037,31 +1558,29 @@ end of a replacement list for either form of macro definition.
 If, in the replacement list of a function-like macro, a parameter is
 immediately preceded or followed by a `##` preprocessing token, the
 parameter is replaced by the corresponding argument’s preprocessing
 token sequence; however, if an argument consists of no preprocessing
 tokens, the parameter is replaced by a placemarker preprocessing token
-instead.[^8]
 For both object-like and function-like macro invocations, before the
 replacement list is reexamined for more macro names to replace, each
 instance of a `##` preprocessing token in the replacement list (not from
 an argument) is deleted and the preceding preprocessing token is
 concatenated with the following preprocessing token. Placemarker
 preprocessing tokens are handled specially: concatenation of two
 placemarkers results in a single placemarker preprocessing token, and
 concatenation of a placemarker with a non-placemarker preprocessing
-token results in the non-placemarker preprocessing token. If the result
-begins with a sequence matching the syntax of
-*universal-character-name*, the behavior is undefined.
-[*Note 1*: This determination does not consider the replacement of
-*universal-character-name*s in translation phase 3
-[[lex.phases]]. — *end note*]
-If the result is not a valid preprocessing token, the behavior is
-undefined. The resulting token is available for further macro
-replacement. The order of evaluation of `##` operators is unspecified.
 [*Example 1*:
 The sequence
@@ -1102,12 +1621,12 @@ fputs("strncmp(\"abc\\0d\", \"abc\", '\\4') == 0: \@n", s);
 #include "vers2.h"      (after macro replacement, before file access)
 "hello";
 "hello, world"
 ```
-Space around the `#` and `##` tokens in the macro definition is
-optional.
 — *end example*]
 [*Example 2*:
@@ -1129,13 +1648,13 @@ in_between(x hash_hash y)
 in_between(x ## y)
 mkstr(x ## y)
 "x ## y"
 ```
-In other words, expanding `hash_hash` produces a new token, consisting
-of two adjacent sharp signs, but this new token is not the `##`
-operator.
 — *end example*]
 [*Example 3*:
@@ -1237,13 +1756,15 @@ macro name.
 ## Line control <a id="cpp.line">[[cpp.line]]</a>
 The *string-literal* of a `#line` directive, if present, shall be a
 character string literal.
-The *line number* of the current source line is one greater than the
-number of new-line characters read or introduced in translation phase 1
-[[lex.phases]] while processing the source file to the current token.
 A preprocessing directive of the form
 ``` bnf
 '# line' digit-sequence new-line
@@ -1251,11 +1772,11 @@ A preprocessing directive of the form
 causes the implementation to behave as if the following sequence of
 source lines begins with a source line that has a line number as
 specified by the digit sequence (interpreted as a decimal integer). If
 the digit sequence specifies zero or a number greater than 2147483647,
-the behavior is undefined.
 A preprocessing directive of the form
 ``` bnf
 '# line' digit-sequence '"' s-char-sequenceₒₚₜ '"' new-line
@@ -1273,25 +1794,33 @@ A preprocessing directive of the form
 (that does not match one of the two previous forms) is permitted. The
 preprocessing tokens after `line` on the directive are processed just as
 in normal text (each identifier currently defined as a macro name is
 replaced by its replacement list of preprocessing tokens). If the
 directive resulting after all replacements does not match one of the two
-previous forms, the behavior is undefined; otherwise, the result is
 processed as appropriate.
 ## Diagnostic directives <a id="cpp.error">[[cpp.error]]</a>
-A preprocessing directive of either of the following forms
 ``` bnf
 '# error' pp-tokensₒₚₜ new-line
 '# warning' pp-tokensₒₚₜ new-line
 ```
-causes the implementation to produce a diagnostic message that should
-include the specified sequence of preprocessing tokens; the `# error`
-directive renders the program ill-formed.
 ## Pragma directive <a id="cpp.pragma">[[cpp.pragma]]</a>
 A preprocessing directive of the form
@@ -1321,20 +1850,20 @@ The following macro names shall be defined by the implementation:
 - **`__cplusplus`**
 The integer literal `202302L`.
-[*Note 1*: Future revisions of C++ will replace the value of this macro
-with a greater value. — *end note*]
-- **The names listed in [[cpp.predefined.ft]].**
 The macros defined in [[cpp.predefined.ft]] shall be defined to the
 corresponding integer literal.
-[*Note 2*: Future revisions of C++ might replace the values of these
-macros with greater values. — *end note*]
 - **`__DATE__`**
 The date of translation of the source file: a character string literal
 of the form `"Mmm dd yyyy"`, where the names of the months are the same
@@ -1343,17 +1872,30 @@ as those generated by the `asctime` function, and the first character of
 translation is not available, an *implementation-defined* valid date
 shall be supplied.
 - **`__FILE__`**
-The presumed name of the current source file (a character string
-literal).[^9]
 - **`__LINE__`**
-The presumed line number (within the current source file) of the current
-source line (an integer literal).[^10]
 - **`__STDC_HOSTED__`**
 The integer literal `1` if the implementation is a hosted implementation
 or the integer literal `0` if it is a freestanding implementation
@@ -1363,37 +1905,37 @@ or the integer literal `0` if it is a freestanding implementation
 An integer literal of type `std::size_t` whose value is the alignment
 guaranteed by a call to `operator new(std::size_t)` or
 `operator new[](std::size_t)`.
-[*Note 3*: Larger alignments will be passed to
 `operator new(std::size_t, std::align_val_t)`, etc.
 [[expr.new]]. — *end note*]
 - **`__STDCPP_FLOAT16_T__`**
 Defined as the integer literal `1` if and only if the implementation
-supports the ISO/IEC/IEEE 60559 floating-point interchange format
-binary16 as an extended floating-point type [[basic.extended.fp]].
 - **`__STDCPP_FLOAT32_T__`**
 Defined as the integer literal `1` if and only if the implementation
-supports the ISO/IEC/IEEE 60559 floating-point interchange format
-binary32 as an extended floating-point type.
 - **`__STDCPP_FLOAT64_T__`**
 Defined as the integer literal `1` if and only if the implementation
-supports the ISO/IEC/IEEE 60559 floating-point interchange format
-binary64 as an extended floating-point type.
 - **`__STDCPP_FLOAT128_T__`**
 Defined as the integer literal `1` if and only if the implementation
-supports the ISO/IEC/IEEE 60559 floating-point interchange format
-binary128 as an extended floating-point type.
 - **`__STDCPP_BFLOAT16_T__`**
 Defined as the integer literal `1` if and only if the implementation
 supports an extended floating-point type with the properties of the
@@ -1421,30 +1963,36 @@ function. If the time of translation is not available, an
 | `__cpp_binary_literals`                 | `201304L` |
 | `__cpp_capture_star_this`               | `201603L` |
 | `__cpp_char8_t`                         | `202207L` |
 | `__cpp_concepts`                        | `202002L` |
 | `__cpp_conditional_explicit`            | `201806L` |
-| `__cpp_constexpr`                       | `202211L` |
 | `__cpp_constexpr_dynamic_alloc`         | `201907L` |
 | `__cpp_constexpr_in_decltype`           | `201711L` |
-| `__cpp_consteval` | `202211L` |
 | `__cpp_constinit`                       | `201907L` |
 | `__cpp_decltype`                        | `200707L` |
 | `__cpp_decltype_auto`                   | `201304L` |
-| `__cpp_deduction_guides`                | `201907L` |
 | `__cpp_delegating_constructors`         | `200604L` |
 | `__cpp_designated_initializers`         | `201707L` |
 | `__cpp_enumerator_attributes`           | `201411L` |
 | `__cpp_explicit_this_parameter`         | `202110L` |
 | `__cpp_fold_expressions`                | `201603L` |
 | `__cpp_generic_lambdas`                 | `201707L` |
 | `__cpp_guaranteed_copy_elision`         | `201606L` |
 | `__cpp_hex_float`                       | `201603L` |
 | `__cpp_if_consteval`                    | `202106L` |
 | `__cpp_if_constexpr`                    | `201606L` |
 | `__cpp_impl_coroutine`                  | `201902L` |
 | `__cpp_impl_destroying_delete`          | `201806L` |
 | `__cpp_impl_three_way_comparison`       | `201907L` |
 | `__cpp_implicit_move`                   | `202207L` |
 | `__cpp_inheriting_constructors`         | `201511L` |
 | `__cpp_init_captures`                   | `201803L` |
 | `__cpp_initializer_lists`               | `200806L` |
@@ -1456,27 +2004,34 @@ function. If the time of translation is not available, an
 | `__cpp_namespace_attributes`            | `201411L` |
 | `__cpp_noexcept_function_type`          | `201510L` |
 | `__cpp_nontype_template_args`           | `201911L` |
 | `__cpp_nontype_template_parameter_auto` | `201606L` |
 | `__cpp_nsdmi`                           | `200809L` |
 | `__cpp_range_based_for`                 | `202211L` |
 | `__cpp_raw_strings`                     | `200710L` |
 | `__cpp_ref_qualifiers`                  | `200710L` |
 | `__cpp_return_type_deduction`           | `201304L` |
 | `__cpp_rvalue_references`               | `200610L` |
 | `__cpp_size_t_suffix`                   | `202011L` |
 | `__cpp_sized_deallocation`              | `201309L` |
-| `__cpp_static_assert`                   | `201411L` |
 | `__cpp_static_call_operator`            | `202207L` |
-| `__cpp_structured_bindings`             | `201606L` |
 | `__cpp_template_template_args`          | `201611L` |
 | `__cpp_threadsafe_static_init`          | `200806L` |
 | `__cpp_unicode_characters`              | `200704L` |
 | `__cpp_unicode_literals`                | `200710L` |
 | `__cpp_user_defined_literals`           | `200809L` |
 | `__cpp_using_enum`                      | `201907L` |
 | `__cpp_variable_templates`              | `201304L` |
 | `__cpp_variadic_templates`              | `200704L` |
 | `__cpp_variadic_using`                  | `201611L` |
 The following macro names are conditionally defined by the
@@ -1513,11 +2068,11 @@ can have more than one thread of execution [[intro.multithread]].
 The values of the predefined macros (except for `__FILE__` and
 `__LINE__`) remain constant throughout the translation unit.
 If any of the pre-defined macro names in this subclause, or the
 identifier `defined`, is the subject of a `#define` or a `#undef`
-preprocessing directive, the behavior is undefined. Any other predefined
 macro names shall begin with a leading underscore followed by an
 uppercase letter or a second underscore.
 ## Pragma operator <a id="cpp.pragma.op">[[cpp.pragma.op]]</a>
@@ -1564,10 +2119,17 @@ LISTING( ..\listing.dir )
 [basic.extended.fp]: basic.md#basic.extended.fp
 [cpp]: #cpp
 [cpp.concat]: #cpp.concat
 [cpp.cond]: #cpp.cond
 [cpp.cond.ha]: #cpp.cond.ha
 [cpp.error]: #cpp.error
 [cpp.import]: #cpp.import
 [cpp.include]: #cpp.include
 [cpp.line]: #cpp.line
 [cpp.module]: #cpp.module
@@ -1582,18 +2144,24 @@ LISTING( ..\listing.dir )
 [cpp.rescan]: #cpp.rescan
 [cpp.scope]: #cpp.scope
 [cpp.stringize]: #cpp.stringize
 [cpp.subst]: #cpp.subst
 [cstdint.syn]: support.md#cstdint.syn
 [expr.const]: expr.md#expr.const
 [expr.new]: expr.md#expr.new
 [intro.compliance]: intro.md#intro.compliance
 [intro.multithread]: basic.md#intro.multithread
 [lex.ccon]: lex.md#lex.ccon
 [lex.digraph]: lex.md#lex.digraph
 [lex.key]: lex.md#lex.key
 [lex.name]: lex.md#lex.name
 [lex.phases]: lex.md#lex.phases
 [lex.token]: lex.md#lex.token
 [module.import]: module.md#module.import
 [support.limits]: support.md#support.limits
@@ -1610,32 +2178,22 @@ LISTING( ..\listing.dir )
 [^3]: As indicated by the syntax, a preprocessing token cannot follow a
     `#else` or `#endif` directive before the terminating new-line
     character. However, comments can appear anywhere in a source file,
     including within a preprocessing directive.
-[^4]: Note that adjacent *string-literal*s are not concatenated into a
-    single *string-literal* (see the translation phases in
-    [[lex.phases]]); thus, an expansion that results in two
-    *string-literal*s is an invalid directive.
-[^5]: Since, by macro-replacement time, all *character-literal*s and
     *string-literal*s are preprocessing tokens, not sequences possibly
     containing identifier-like subsequences (see [[lex.phases]],
     translation phases), they are never scanned for macro names or
     parameters.
-[^6]: An alternative token [[lex.digraph]] is not an identifier, even
     when its spelling consists entirely of letters and underscores.
     Therefore it is not possible to define a macro whose name is the
     same as that of an alternative token.
-[^7]: A *conditionally-supported-directive* is a preprocessing directive
     regardless of whether the implementation supports it.
-[^8]: Placemarker preprocessing tokens do not appear in the syntax
     because they are temporary entities that exist only within
     translation phase 4.
-[^9]: The presumed source file name can be changed by the `#line`
-    directive.
-[^10]: The presumed line number can be changed by the `#line` directive.

 ``` bnf
 control-line:
     '# include' pp-tokens new-line
     pp-import
+    '# embed ' pp-tokens new-line
     '# define ' identifier replacement-list new-line
     '# define ' identifier lparen identifier-listₒₚₜ ')' replacement-list new-line
     '# define ' identifier lparen '... )' replacement-list new-line
     '# define ' identifier lparen identifier-list ', ... )' replacement-list new-line
     '# undef ' identifier new-line
     '# ifndef ' identifier new-line groupₒₚₜ
 ```
 ``` bnf
 elif-groups:
+    elif-group elif-groupsₒₚₜ
 ```
 ``` bnf
 elif-group:
     '# elif ' constant-expression new-line groupₒₚₜ
     pp-tokensₒₚₜ
 ```
 ``` bnf
 pp-tokens:
+    preprocessing-token pp-tokensₒₚₜ
+```
+``` bnf
+embed-parameter-seq:
+    embed-parameter embed-parameter-seqₒₚₜ
+```
+``` bnf
+embed-parameter:
+    embed-standard-parameter
+    embed-prefixed-parameter
+```
+``` bnf
+embed-standard-parameter:
+    'limit' '(' pp-balanced-token-seq ')'
+    'prefix' '(' pp-balanced-token-seqₒₚₜ ')'
+    'suffix' '(' pp-balanced-token-seqₒₚₜ ')'
+    'if_empty' '(' pp-balanced-token-seqₒₚₜ ')'
+```
+``` bnf
+embed-prefixed-parameter:
+    identifier :: identifier
+    identifier :: identifier '(' pp-balanced-token-seqₒₚₜ ')'
+```
+``` bnf
+pp-balanced-token-seq:
+    pp-balanced-token pp-balanced-token-seqₒₚₜ
+```
+``` bnf
+pp-balanced-token:
+    '(' pp-balanced-token-seqₒₚₜ ')'
+    '[' pp-balanced-token-seqₒₚₜ ']'
+    '{' pp-balanced-token-seqₒₚₜ '}'
+    any pp-token except:
+       parenthesis (U+0028 (left parenthesis) and U+0029 (right parenthesis)),
+       bracket (U+005b (left square bracket) and U+005d (right square bracket)), or
+       brace (U+007b (left curly bracket) and U+007d (right curly bracket)).
 ```
 ``` bnf
 new-line:
     the new-line character
 ```
+The implementation can process and skip sections of source files
+conditionally, include other source files, import macros from header
+units, and replace macros. These capabilities are called
+*preprocessing*, because conceptually they occur before translation of
+the resulting translation unit.
 A *preprocessing directive* consists of a sequence of preprocessing
 tokens that satisfies the following constraints: At the start of
+translation phase 4, the first preprocessing token in the sequence,
+referred to as a *directive-introducing token*, begins with the first
+character in the source file (optionally after whitespace containing no
+new-line characters) or follows whitespace containing at least one
+new-line character, and is
 - a `#` preprocessing token, or
 - an `import` preprocessing token immediately followed on the same
+  logical source line by a *header-name*, `<`, *identifier*,
+ *string-literal*, or `:` preprocessing token, or
 - a `module` preprocessing token immediately followed on the same
+  logical source line by an *identifier*, `:`, or `;` preprocessing
+  token, or
 - an `export` preprocessing token immediately followed on the same
+  logical source line by one of the two preceding forms.
+The last preprocessing token in the sequence is the first preprocessing
+token within the sequence that is immediately followed by whitespace
+containing a new-line character.[^1]
 [*Note 1*: A new-line character ends the preprocessing directive even
 if it occurs within what would otherwise be an invocation of a
 function-like macro. — *end note*]
 ```
 — *end example*]
 A sequence of preprocessing tokens is only a *text-line* if it does not
+begin with a directive-introducing token.
+[*Example 2*:
+``` cpp
+using module = int;
+module i;               // not a text-line and not a control-line
+int foo() {
+  return i;
+}
+```
+The example is not a valid *preprocessing-file*.
+— *end example*]
+A sequence of preprocessing tokens is only a
+*conditionally-supported-directive* if it does not begin with any of the
+directive names appearing after a `#` in the syntax. A
+*conditionally-supported-directive* is conditionally-supported with
+*implementation-defined* semantics.
+If one of the *pp-tokens* of a `#embed` directive (before macro
+replacement) is the *identifier* `limit`, `prefix`, `suffix`, or
+`if_empty` and that *identifier* is defined as a macro
+[[cpp.replace.general]], the program is ill-formed. Any
+*embed-prefixed-parameter* is conditionally-supported, with
+*implementation-defined* semantics.
 At the start of phase 4 of translation, the *group* of a
 *pp-global-module-fragment* shall contain neither a *text-line* nor a
 *pp-import*.
 the directive name and the following new-line character.
 The only whitespace characters that shall appear between preprocessing
 tokens within a preprocessing directive (from just after the
 directive-introducing token through just before the terminating new-line
+character) are U+0020 (space) and U+0009 (character tabulation)
+(including spaces that have replaced comments or possibly other
+whitespace characters in translation phase 3).
 The preprocessing tokens within a preprocessing directive are not
 subject to macro expansion unless otherwise stated.
+[*Example 3*:
 In:
 ``` cpp
 #define EMPTY
     any *preprocessing-token* other than '>'
 ```
 ``` bnf
 h-pp-tokens:
+    h-preprocessing-token h-pp-tokensₒₚₜ
 ```
 ``` bnf
 header-name-tokens:
     string-literal
 has-include-expression:
     '__has_include' '(' header-name ')'
     '__has_include' '(' header-name-tokens ')'
 ```
+``` bnf
+has-embed-expression:
+    '__has_embed' '(' header-name pp-balanced-token-seqₒₚₜ ')'
+    '__has_embed' '(' header-name-tokens pp-balanced-token-seqₒₚₜ ')'
+```
 ``` bnf
 has-attribute-expression:
     '__has_cpp_attribute (' pp-tokens ')'
 ```
 The expression that controls conditional inclusion shall be an integral
 constant expression except that identifiers (including those lexically
 identical to keywords) are interpreted as described below[^2]
+and it may contain zero or more *defined-macro-expression*s,
+*has-include-expression*s, *has-attribute-expression*s, and/or
+*has-embed-expression*s as unary operator expressions. A
+*defined-macro-expression* shall not appear within a
+*has-include-expression* or *has-embed-expression*.
 A *defined-macro-expression* evaluates to `1` if the identifier is
 currently defined as a macro name (that is, if it is predefined or if it
 has one or more active macro definitions [[cpp.import]], for example
 because it has been the subject of a `#define` preprocessing directive
 without an intervening `#undef` directive with the same subject
 identifier), `0` if it is not.
 The header or source file identified by the parenthesized preprocessing
 token sequence in each contained *has-include-expression* is searched
+for as if that preprocessing token sequence were the *pp-tokens* of a
 `#include` directive, except that no further macro expansion is
+performed. If the preprocessing token sequence does not consist solely
+of a *header-name* or cannot be combined [[cpp.include]] into a single
+*header-name* preprocessing token, the program is ill-formed. The
 *has-include-expression* evaluates to `1` if the search for the source
 file succeeds, and to `0` if the search fails.
+The parenthesized preprocessing token sequence of each contained
+*has-embed-expression* is processed as if that preprocessing token
+sequence were the *pp-tokens* of a `#embed` directive [[cpp.embed]],
+except that no further macro expansion is performed. The
+*has-embed-expression* evaluates to:
+- `__STDC_EMBED_FOUND__` if the search for the resource succeeds, all
+  the given *embed-parameter*s in the *embed-parameter-seq* are
+  supported, and the resource is not empty.
+- Otherwise, `__STDC_EMBED_EMPTY__` if the search for the resource
+  succeeds, all the given *embed-parameter*s in the
+  *embed-parameter-seq* are supported, and the resource is empty.
+- Otherwise, `__STDC_EMBED_NOT_FOUND__`.
+[*Note 1*: An unrecognized *embed-parameter* in an
+*has-embed-expression* is not ill-formed and is instead treated as not
+supported. — *end note*]
 Each *has-attribute-expression* is replaced by a non-zero *pp-number*
 matching the form of an *integer-literal* if the implementation supports
 an attribute with the name specified by interpreting the *pp-tokens*,
 after macro expansion, as an *attribute-token*, and by `0` otherwise.
 The program is ill-formed if the *pp-tokens* do not match the form of an
 *attribute-token*.
+For an attribute specified in this document, it is
+*implementation-defined* whether the value of the
+*has-attribute-expression* is `0` or is given by [[cpp.cond.ha]]. For
+other attributes recognized by the implementation, the value is
 *implementation-defined*.
+[*Note 2*: It is expected that the availability of an attribute can be
 detected by any non-zero result. — *end note*]
 **Table: __has_cpp_attribute values** <a id="cpp.cond.ha">[cpp.cond.ha]</a>
 | Attribute           | Value     |
+| ------------------- | --------- |
 | `assume`            | `202207L` |
 | `deprecated`        | `201309L` |
 | `fallthrough`       | `201603L` |
+| `indeterminate`     | `202403L` |
 | `likely`            | `201803L` |
 | `maybe_unused`      | `201603L` |
 | `no_unique_address` | `201803L` |
 | `nodiscard`         | `201907L` |
 | `noreturn`          | `200809L` |
 | `unlikely`          | `201803L` |
 The `#ifdef`, `#ifndef`, `#elifdef`, and `#elifndef` directives, and the
+`defined` conditional inclusion operator, shall treat `__has_include`,
+`__has_embed`, and `__has_cpp_attribute` as if they were the names of
+defined macros. The identifiers `__has_include`, `__has_embed`, and
+`__has_cpp_attribute` shall not appear in any context not mentioned in
+this subclause.
 Each preprocessing token that remains (in the list of preprocessing
 tokens that will become the controlling expression) after all macro
 replacements have occurred shall be in the lexical form of a token
 [[lex.token]].
 check whether the controlling constant expression evaluates to nonzero.
 Prior to evaluation, macro invocations in the list of preprocessing
 tokens that will become the controlling constant expression are replaced
 (except for those macro names modified by the `defined` unary operator),
+just as in normal text. If replacement of macros in the preprocessing
+tokens following the sequence `\xname{has_embed} (` and before a
+matching `)` (possibly produced by macro expansion) encounters a
+preprocessing token that is one of the *identifier*s `limit`, `prefix`,
+`suffix`, or `if_empty` and that *identifier* is defined as a macro
+[[cpp.replace.general]], the program is ill-formed. If the preprocessing
+token `defined` is generated as a result of this replacement process or
+use of the `defined` unary operator does not match one of the two
+specified forms prior to macro replacement, the program is ill-formed,
+no diagnostic required.
 After all replacements due to macro expansion and evaluations of
+*defined-macro-expression*s, *has-include-expression*s,
+*has-embed-expression*s, and *has-attribute-expression*s have been
+performed, all remaining identifiers and keywords, except for `true` and
+`false`, are replaced with the *pp-number* `0`, and then each
+preprocessing token is converted into a token.
+[*Note 3*: An alternative token [[lex.digraph]] is not an identifier,
 even when its spelling consists entirely of letters and underscores.
 Therefore it is not subject to this replacement. — *end note*]
 The resulting tokens comprise the controlling constant expression which
 is evaluated according to the rules of  [[expr.const]] using arithmetic
 that has at least the ranges specified in  [[support.limits]]. For the
 purposes of this token conversion and evaluation all signed and unsigned
 integer types act as if they have the same representation as,
 respectively, `intmax_t` or `uintmax_t` [[cstdint.syn]].
+[*Note 4*: Thus on an implementation where
 `std::numeric_limits<int>::max()` is `0x7FFF` and
 `std::numeric_limits<unsigned int>::max()` is `0xFFFF`, the integer
 literal `0x8000` is signed and positive within a `#if` expression even
 though it is unsigned in translation phase 7
 [[lex.phases]]. — *end note*]
 This includes interpreting *character-literal*s according to the rules
 in [[lex.ccon]].
+[*Note 5*: The associated character encodings of literals are the same
 in `#if` and `#elif` directives and in any expression. — *end note*]
 Each subexpression with type `bool` is subjected to integral promotion
 before processing continues.
 `#if` `!defined` *identifier*, `#elif` `defined` *identifier*, and
 `#elif` `!defined` *identifier*, respectively.
 Each directive’s condition is checked in order. If it evaluates to false
 (zero), the group that it controls is skipped: directives are processed
+only through the directive name that determines the directive in order
+to keep track of the level of nested conditionals; the rest of the
+directives’ preprocessing tokens are ignored, as are the other
+preprocessing tokens in the group. Only the first group whose control
+condition evaluates to true (nonzero) is processed; any following groups
+are skipped and their controlling directives are processed as if they
+were in a group that is skipped. If none of the conditions evaluates to
+true, and there is a `#else` directive, the group controlled by the
+`#else` is processed; lacking a `#else` directive, all the groups until
+the `#endif` are skipped.[^3]
 [*Example 1*:
 This demonstrates a way to include a library `optional` facility only if
 it is available:
 — *end example*]
 ## Source file inclusion <a id="cpp.include">[[cpp.include]]</a>
+A *header search* for a sequence of characters searches a sequence of
+places for a header identified uniquely by that sequence of characters.
+How the places are determined or the header identified is
+*implementation-defined*.
+A *source file search* for a sequence of characters attempts to identify
+a source file that is named by the sequence of characters. The named
+source file is searched for in an *implementation-defined* manner. If
+the implementation does not support a source file search for that
+sequence of characters, or if the search fails, the result of the source
+file search is the result of a header search for the same sequence of
+characters.
 A preprocessing directive of the form
 ``` bnf
+'# include' header-name new-line
 ```
 causes the replacement of that directive by the entire contents of the
+header or source file identified by *header-name*.
+If the *header-name* is of the form
+``` bnf
+'<' h-char-sequence '>'
+```
+a header is identified by a header search for the sequence of characters
+of the *h-char-sequence*.
+If the *header-name* is of the form
 ``` bnf
+'"' q-char-sequence '"'
 ```
+the source file or header is identified by a source file search for the
+sequence of characters of the *q-char-sequence*.
+If a header search fails, or if a source file search or header search
+identifies a header or source file that cannot be processed by the
+implementation, the program is ill-formed.
+[*Note 1*: If the header or source file cannot be processed, the
+program is ill-formed even when evaluating
+`__has_include`. — *end note*]
 A preprocessing directive of the form
 ``` bnf
 '# include' pp-tokens new-line
 ```
+(that does not match the previous form) is permitted. The preprocessing
+tokens after `include` in the directive are processed just as in normal
+text (i.e., each identifier currently defined as a macro name is
+replaced by its replacement list of preprocessing tokens). Then, an
+attempt is made to form a *header-name* preprocessing token
+[[lex.header]] from the whitespace and the characters of the spellings
+of the resulting sequence of preprocessing tokens; the treatment of
+whitespace is *implementation-defined*. If the attempt succeeds, the
+directive with the so-formed *header-name* is processed as specified for
+the previous form. Otherwise, the program is ill-formed, no diagnostic
+required.
+[*Note 2*: Adjacent *string-literal*s are not concatenated into a
+single *string-literal* (see the translation phases in  [[lex.phases]]);
+thus, an expansion that results in two *string-literal*s is an invalid
+directive. — *end note*]
 The implementation shall provide unique mappings for sequences
 consisting of one or more *nondigit*s or *digit*s [[lex.name]] followed
 by a period (`.`) and a single *nondigit*. The first character shall not
 be a *digit*. The implementation may ignore distinctions of alphabetical
 header [[module.import]], it is *implementation-defined* whether the
 `#include` preprocessing directive is instead replaced by an `import`
 directive [[cpp.import]] of the form
 ``` bnf
+import header-name ';' new-line
 ```
+[*Note 3*:
 An implementation can provide a mechanism for making arbitrary source
 files available to the `< >` search. However, using the `< >` form for
 headers provided with the implementation and the `" "` form for sources
 outside the control of the implementation achieves wider portability.
 #include INCFILE
 ```
 — *end example*]
+## Resource inclusion <a id="cpp.embed">[[cpp.embed]]</a>
+### General <a id="cpp.embed.gen">[[cpp.embed.gen]]</a>
+A *bracket resource search* for a sequence of characters searches a
+sequence of places for a resource identified uniquely by that sequence
+of characters. How the places are determined or the resource identified
+is *implementation-defined*.
+A *quote resource search* for a sequence of characters attempts to
+identify a resource that is named by the sequence of characters. The
+named resource is searched for in an *implementation-defined* manner. If
+the implementation does not support a quote resource search for that
+sequence of characters, or if the search fails, the result of the quote
+resource search is the result of a bracket resource search for the same
+sequence of characters.
+A preprocessing directive of the form
+``` bnf
+'# embed' header-name pp-tokensₒₚₜ new-line
+```
+causes the replacement of that directive by preprocessing tokens derived
+from data in the resource identified by *header-name*, as specified
+below.
+If the *header-name* is of the form
+``` bnf
+'<' h-char-sequence '>'
+```
+the resource is identified by a bracket resource search for the sequence
+of characters of the *h-char-sequence*.
+If the *header-name* is of the form
+``` bnf
+'"' q-char-sequence '"'
+```
+the resource is identified by a quote resource search for the sequence
+of characters of the *q-char-sequence*.
+If a bracket resource search fails, or if a quote or bracket resource
+search identifies a resource that cannot be processed by the
+implementation, the program is ill-formed.
+[*Note 1*: If the resource cannot be processed, the program is
+ill-formed even when processing `#embed` with `limit(0)`
+[[cpp.embed.param.limit]] or evaluating `__has_embed`. — *end note*]
+*Recommended practice:* A mechanism similar to, but distinct from, the
+*implementation-defined* search paths used for `#include`
+[[cpp.include]] is encouraged.
+Either form of the `#embed` directive processes the *pp-tokens*, if
+present, just as in normal text. The *pp-tokens* shall then have the
+form *embed-parameter-seq*.
+A resource is a source of data accessible from the translation
+environment. A resource has an *implementation-resource-width*, which is
+the *implementation-defined* size in bits of the resource. If the
+implementation-resource-width is not an integral multiple of `CHAR_BIT`,
+the program is ill-formed. Let *implementation-resource-count* be
+implementation-resource-width divided by `CHAR_BIT`. Every resource also
+has a *resource-count*, which is
+- the value as computed from the optionally-provided `limit`
+  *embed-parameter* [[cpp.embed.param.limit]], if present;
+- otherwise, the implementation-resource-count.
+A resource is empty if the resource-count is zero.
+[*Example 1*:
+``` cpp
+// ill-formed if the implementation-resource-width is 6 bits
+#embed "6_bits.bin"
+```
+— *end example*]
+The `#embed` directive is replaced by a comma-separated list of integer
+literals of type `int`, unless otherwise modified by embed parameters
+[[cpp.embed.param]].
+The integer literals in the comma-separated list correspond to
+resource-count consecutive calls to `std::fgetc` [[cstdio.syn]] from the
+resource, as a binary file. If any call to `std::fgetc` returns `EOF`,
+the program is ill-formed.
+*Recommended practice:* The value of each integer literal should closely
+represent the bit stream of the resource unmodified. This can require an
+implementation to consider potential differences between translation and
+execution environments, as well as any other applicable sources of
+mismatch.
+[*Example 2*:
+``` cpp
+#include <cstring>
+#include <cstddef>
+#include <fstream>
+#include <vector>
+#include <cassert>
+int main() {
+  // If the file is the same as the resource in the translation environment, no assert in this program should fail.
+  constexpr unsigned char d[] = {
+#embed <data.dat>
+  };
+  const std::vector<unsigned char> vec_d = {
+#embed <data.dat>
+  };
+  constexpr std::size_t expected_size = sizeof(d);
+  // same file in execution environment as was embedded
+  std::ifstream f_source("data.dat", std::ios::binary | std::ios::in);
+  unsigned char runtime_d[expected_size];
+  char* ifstream_ptr = reinterpret_cast<char*>(runtime_d);
+  assert(!f_source.read(ifstream_ptr, expected_size));
+  std::size_t ifstream_size = f_source.gcount();
+  assert (ifstream_size == expected_size);
+  int is_same = std::memcmp(&d[0], ifstream_ptr, ifstream_size);
+  assert(is_same == 0);
+  int is_same_vec = std::memcmp(vec_d.data(), ifstream_ptr, ifstream_size);
+  assert(is_same_vec == 0);
+}
+```
+— *end example*]
+[*Example 3*:
+``` cpp
+int i = {
+#embed "i.dat"
+};  // well-formed if i.dat produces a single value
+int i2 =
+#embed "i.dat"
+;   // also well-formed if i.dat produces a single value
+struct s {
+  double a, b, c;
+  struct { double e, f, g; } x;
+  double h, i, j;
+};
+s x = {
+// well-formed if the directive produces nine or fewer values
+#embed "s.dat"
+};
+```
+— *end example*]
+A preprocessing directive of the form
+``` bnf
+'# embed' pp-tokens new-line
+```
+(that does not match the previous form) is permitted. The preprocessing
+tokens after `embed` in the directive are processed just as in normal
+text (i.e., each identifier currently defined as a macro name is
+replaced by its replacement list of preprocessing tokens). Then, an
+attempt is made to form a *header-name* preprocessing token
+[[lex.header]] from the whitespace and the characters of the spellings
+of the resulting sequence of preprocessing tokens immediately after
+`embed`; the treatment of whitespace is *implementation-defined*. If the
+attempt succeeds, the directive with the so-formed *header-name* is
+processed as specified for the previous form. Otherwise, the program is
+ill-formed.
+[*Note 2*: Adjacent *string-literal*s are not concatenated into a
+single *string-literal* (see the translation phases in  [[lex.phases]]);
+thus, an expansion that results in two *string-literal*s is an invalid
+directive. — *end note*]
+Any further processing as in normal text described for the previous form
+is not performed.
+[*Note 3*: That is, processing as in normal text happens once and only
+once for the entire directive. — *end note*]
+[*Example 4*:
+If the directive matches the second form, the whole directive is
+replaced. If the directive matches the first form, everything after the
+*header-name* is replaced.
+``` cpp
+#define EMPTY
+#define X myfile
+#define Y rsc
+#define Z 42
+#embed <myfile.rsc> prefix(Z)
+#embed EMPTY <X.Y>  prefix(Z)
+```
+is equivalent to:
+``` cpp
+#embed <myfile.rsc> prefix(42)
+#embed <myfile.rsc> prefix(42)
+```
+— *end example*]
+### Embed parameters <a id="cpp.embed.param">[[cpp.embed.param]]</a>
+#### limit parameter <a id="cpp.embed.param.limit">[[cpp.embed.param.limit]]</a>
+An *embed-parameter* of the form `limit (` *pp-balanced-token-seq* `)`
+specifies the maximum possible number of elements in the comma-delimited
+list. It shall appear at most once in the *embed-parameter-seq*. The
+preprocessing token `defined` shall not appear in the
+*pp-balanced-token-seq*.
+The *pp-balanced-token-seq* is evaluated as a *constant-expression*
+using the rules as described in conditional inclusion [[cpp.cond]], but
+without being processed as in normal text an additional time.
+[*Example 1*:
+``` cpp
+#undef DATA_LIMIT
+#if __has_embed(<data.dat> limit(DATA_LIMIT))
+#endif
+```
+is equivalent to:
+``` cpp
+#if __has_embed(<data.dat> limit(0))
+#endif
+```
+— *end example*]
+[*Example 2*:
+``` cpp
+#embed <data.dat> limit(__has_include("a.h"))
+#if __has_embed(<data.dat> limit(__has_include("a.h")))
+// ill-formed: __has_include[cpp.cond] cannot appear here
+#endif
+```
+— *end example*]
+The *constant-expression* shall be an integral constant expression whose
+value is greater than or equal to zero. The resource-count
+[[cpp.embed.gen]] becomes implementation-resource-count, if the value of
+the *constant-expression* is greater than implementation-resource-count;
+otherwise, the value of the *constant-expression*.
+[*Example 3*:
+``` cpp
+constexpr unsigned char sound_signature[] = {
+  // a hypothetical resource capable of expanding to four or more elements
+#embed <sdk/jump.wav> limit(2+2)
+};
+static_assert(sizeof(sound_signature) == 4);    // OK
+```
+— *end example*]
+#### prefix parameter <a id="cpp.embed.param.prefix">[[cpp.embed.param.prefix]]</a>
+An *embed-parameter* of the form
+``` bnf
+'prefix (' pp-balanced-token-seqₒₚₜ ')'
+```
+shall appear at most once in the *embed-parameter-seq*.
+If the resource is empty, this *embed-parameter* is ignored. Otherwise,
+the *pp-balanced-token-seq* is placed immediately before the
+comma-delimited list of integral literals.
+#### suffix parameter <a id="cpp.embed.param.suffix">[[cpp.embed.param.suffix]]</a>
+An *embed-parameter* of the form
+``` bnf
+'suffix (' pp-balanced-token-seqₒₚₜ ')'
+```
+shall appear at most once in the *embed-parameter-seq*.
+If the resource is empty, this *embed-parameter* is ignored. Otherwise,
+the *pp-balanced-token-seq* is placed immediately after the
+comma-delimited list of the integral constant expressions.
+[*Example 1*:
+``` cpp
+constexpr unsigned char whl[] = {
+#embed "ches.glsl" \
+  prefix(0xEF, 0xBB, 0xBF, ) /* a sequence of bytes */ \
+  suffix(,)
+  0
+};
+// always null-terminated, contains the sequence if not empty
+constexpr bool is_empty = sizeof(whl) == 1 && whl[0] == '\0';
+constexpr bool is_not_empty = sizeof(whl) >= 4
+  && whl[sizeof(whl) - 1] == '\0'
+  && whl[0] == '\xEF' && whl[1] == '\xBB' && whl[2] == '\xBF';
+static_assert(is_empty || is_not_empty);
+```
+— *end example*]
+#### `if_empty` parameter <a id="cpp.embed.param.if.empty">[[cpp.embed.param.if.empty]]</a>
+An embed-parameter of the form
+``` bnf
+'if_empty (' pp-balanced-token-seqₒₚₜ ')'
+```
+shall appear at most once in the *embed-parameter-seq*.
+If the resource is not empty, this *embed-parameter* is ignored.
+Otherwise, the `#embed` directive is replaced by the
+*pp-balanced-token-seq*.
+[*Example 1*:
+`limit(0)` affects when a resource is considered empty. Therefore, the
+following program:
+``` cpp
+#embed </owo/uwurandom> \
+  if_empty(42203) limit(0)
+```
+expands to
+``` cpp
+42203
+```
+— *end example*]
+[*Example 2*:
+This resource is considered empty due to the `limit(0)`
+*embed-parameter*, always, including in `__has_embed` clauses.
+``` cpp
+int infinity_zero () {
+#if __has_embed(</owo/uwurandom> limit(0) prefix(some tokens)) == __STDC_EMBED_EMPTY__
+  // if </owo/uwurandom> exists, this conditional inclusion branch is taken and the function returns 0.
+  return 0;
+#else
+  // otherwise, the resource does not exist
+#error "The resource does not exist"
+#endif
+}
+```
+— *end example*]
 ## Module directive <a id="cpp.module">[[cpp.module]]</a>
 ``` bnf
 pp-module:
     exportₒₚₜ module pp-tokensₒₚₜ ';' new-line
 ```
 A *pp-module* shall not appear in a context where `module` or (if it is
+the first preprocessing token of the *pp-module*) `export` is an
+identifier defined as an object-like macro.
+The *pp-tokens*, if any, of a *pp-module* shall be of the form:
+``` bnf
+pp-module-name pp-module-partitionₒₚₜ pp-tokensₒₚₜ
+```
+where the *pp-tokens* (if any) shall not begin with a `(` preprocessing
+token and the grammar non-terminals are defined as:
+``` bnf
+pp-module-name:
+    pp-module-name-qualifierₒₚₜ identifier
+```
+``` bnf
+pp-module-partition:
+    ':' pp-module-name-qualifierₒₚₜ identifier
+```
+``` bnf
+pp-module-name-qualifier:
+    identifier '.'
+    pp-module-name-qualifier identifier '.'
+```
+No *identifier* in the *pp-module-name* or *pp-module-partition* shall
+currently be defined as an object-like macro.
 Any preprocessing tokens after the `module` preprocessing token in the
 `module` directive are processed just as in normal text.
 [*Note 1*: Each identifier currently defined as a macro name is
     exportₒₚₜ import header-name-tokens pp-tokensₒₚₜ ';' new-line
     exportₒₚₜ import pp-tokens ';' new-line
 ```
 A *pp-import* shall not appear in a context where `import` or (if it is
+the first preprocessing token of the *pp-import*) `export` is an
+identifier defined as an object-like macro.
 The preprocessing tokens after the `import` preprocessing token in the
 `import` *control-line* are processed just as in normal text (i.e., each
 identifier currently defined as a macro name is replaced by its
 replacement list of preprocessing tokens).
   unit is the first point at which a `#undef` directive naming the macro
   occurs after its point of definition, or the first point of macro
   import of a header unit containing a point of undefinition for the
   macro definition, whichever (if any) occurs first.
+A macro definition is *active* at a source location if it has a point of
 definition in that translation unit preceding the location, and does not
 have a point of undefinition in that translation unit preceding the
 location.
 If a macro would be replaced or redefined, and multiple macro
 name*. There is one name space for macro names. Any whitespace
 characters preceding or following the replacement list of preprocessing
 tokens are not considered part of the replacement list for either form
 of macro.
+A translation unit shall not `#define` or `#undef` macro names lexically
+identical to keywords, to the identifiers listed in
+[[lex.name.special]], or to the *attribute-token*s described in
+[[dcl.attr]], except that the macro names `likely` and `unlikely` may be
+defined as function-like macros.
 If a `#` preprocessing token, followed by an identifier, occurs
 lexically at the point at which a preprocessing directive can begin, the
 identifier is not subject to macro replacement.
 A preprocessing directive of the form
 ``` bnf
 '# define' identifier replacement-list new-line
 ```
 defines an *object-like macro* that causes each subsequent instance of
+the macro name[^4]
 to be replaced by the replacement list of preprocessing tokens that
+constitute the remainder of the directive.[^5]
 The replacement list is then rescanned for more macro names as specified
+in [[cpp.rescan]].
 [*Example 2*:
 The simplest use of this facility is to define a “manifest constant”, as
 in
 matching parentheses forms the list of arguments for the function-like
 macro. The individual arguments within the list are separated by comma
 preprocessing tokens, but comma preprocessing tokens between matching
 inner parentheses do not separate arguments. If there are sequences of
 preprocessing tokens within the list of arguments that would otherwise
+act as preprocessing directives,[^6]
+the program is ill-formed.
 [*Example 3*:
 The following defines a function-like macro whose value is the maximum
 of its arguments. It has the disadvantages of evaluating one or the
 After the arguments for the invocation of a function-like macro have
 been identified, argument substitution takes place. For each parameter
 in the replacement list that is neither preceded by a `#` or `##`
 preprocessing token nor followed by a `##` preprocessing token, the
+preprocessing tokens naming the parameter are replaced by a
+preprocessing token sequence determined as follows:
 - If the parameter is of the form *va-opt-replacement*, the replacement
   preprocessing tokens are the preprocessing token sequence for the
   corresponding argument, as specified below.
 - Otherwise, the replacement preprocessing tokens are the preprocessing
   tokens of corresponding argument after all macros contained therein
   have been expanded. The argument’s preprocessing tokens are completely
   macro replaced before being substituted as if they formed the rest of
+  the preprocessing translation unit with no other preprocessing tokens
+ being available.
 [*Example 1*:
 ``` cpp
 #define LPAREN() (
 character string literal. Whitespace before the first preprocessing
 token and after the last preprocessing token comprising the stringizing
 argument is deleted. Otherwise, the original spelling of each
 preprocessing token in the stringizing argument is retained in the
 character string literal, except for special handling for producing the
+spelling of *header-name*s, *character-literal*s, and *string-literal*s
+(including the delimiting U+0022 (quotation mark) (`"`)) contained
+within the preprocessing token: a U+005c (reverse solidus) character
+(`\`) is inserted before each U+0022 (quotation mark) and
+U+005c (reverse solidus) character of a *header-name*,
+*character-literal*, or *string-literal*, and each new-line character is
+replaced by the two-character sequence `\n`. If the replacement that
+results is not a valid character string literal, the program is
+ill-formed. The character string literal corresponding to an empty
+stringizing argument is `""`. The order of evaluation of `#` and `##`
+operators is unspecified.
 ### The `##` operator <a id="cpp.concat">[[cpp.concat]]</a>
 A `##` preprocessing token shall not occur at the beginning or at the
 end of a replacement list for either form of macro definition.
 If, in the replacement list of a function-like macro, a parameter is
 immediately preceded or followed by a `##` preprocessing token, the
 parameter is replaced by the corresponding argument’s preprocessing
 token sequence; however, if an argument consists of no preprocessing
 tokens, the parameter is replaced by a placemarker preprocessing token
+instead.[^7]
 For both object-like and function-like macro invocations, before the
 replacement list is reexamined for more macro names to replace, each
 instance of a `##` preprocessing token in the replacement list (not from
 an argument) is deleted and the preceding preprocessing token is
 concatenated with the following preprocessing token. Placemarker
 preprocessing tokens are handled specially: concatenation of two
 placemarkers results in a single placemarker preprocessing token, and
 concatenation of a placemarker with a non-placemarker preprocessing
+token results in the non-placemarker preprocessing token.
+[*Note 1*: Concatenation can form a *universal-character-name*
+[[lex.charset]]. — *end note*]
+If the result is not a valid preprocessing token, the program is
+ill-formed. The resulting preprocessing token is available for further
+macro replacement. The order of evaluation of `##` operators is
+unspecified.
 [*Example 1*:
 The sequence
 #include "vers2.h"      (after macro replacement, before file access)
 "hello";
 "hello, world"
 ```
+Space around the `#` and `##` preprocessing tokens in the macro
+definition is optional.
 — *end example*]
 [*Example 2*:
 in_between(x ## y)
 mkstr(x ## y)
 "x ## y"
 ```
+In other words, expanding `hash_hash` produces a new preprocessing
+token, consisting of two adjacent sharp signs, but this new
+preprocessing token is not the `##` operator.
 — *end example*]
 [*Example 3*:
 ## Line control <a id="cpp.line">[[cpp.line]]</a>
 The *string-literal* of a `#line` directive, if present, shall be a
 character string literal.
+The *line number* of the current source line is the line number of the
+current physical source line, i.e., it is one greater than the number of
+new-line characters read or introduced in translation phase 1
+[[lex.phases]] while processing the source file to the current
+preprocessing token.
 A preprocessing directive of the form
 ``` bnf
 '# line' digit-sequence new-line
 causes the implementation to behave as if the following sequence of
 source lines begins with a source line that has a line number as
 specified by the digit sequence (interpreted as a decimal integer). If
 the digit sequence specifies zero or a number greater than 2147483647,
+the program is ill-formed.
 A preprocessing directive of the form
 ``` bnf
 '# line' digit-sequence '"' s-char-sequenceₒₚₜ '"' new-line
 (that does not match one of the two previous forms) is permitted. The
 preprocessing tokens after `line` on the directive are processed just as
 in normal text (each identifier currently defined as a macro name is
 replaced by its replacement list of preprocessing tokens). If the
 directive resulting after all replacements does not match one of the two
+previous forms, the program is ill-formed; otherwise, the result is
 processed as appropriate.
 ## Diagnostic directives <a id="cpp.error">[[cpp.error]]</a>
+A preprocessing directive of the form
 ``` bnf
 '# error' pp-tokensₒₚₜ new-line
+```
+renders the program ill-formed. A preprocessing directive of the form
+``` bnf
 '# warning' pp-tokensₒₚₜ new-line
 ```
+requires the implementation to produce at least one diagnostic message
+for the preprocessing translation unit [[intro.compliance.general]].
+*Recommended practice:* Any diagnostic message caused by either of these
+directives should include the specified sequence of preprocessing
+tokens.
 ## Pragma directive <a id="cpp.pragma">[[cpp.pragma]]</a>
 A preprocessing directive of the form
 - **`__cplusplus`**
 The integer literal `202302L`.
+[*Note 1*: Future revisions of this document will replace the value of
+this macro with a greater value. — *end note*]
+- **The macro names listed in [[cpp.predefined.ft]].**
 The macros defined in [[cpp.predefined.ft]] shall be defined to the
 corresponding integer literal.
+[*Note 2*: Future revisions of this document might replace the values
+of these macros with greater values. — *end note*]
 - **`__DATE__`**
 The date of translation of the source file: a character string literal
 of the form `"Mmm dd yyyy"`, where the names of the months are the same
 translation is not available, an *implementation-defined* valid date
 shall be supplied.
 - **`__FILE__`**
+A character string literal representing the presumed name of the current
+source file.
+[*Note 3*: The presumed source file name can be changed by the `#line`
+directive [[cpp.line]]. — *end note*]
 - **`__LINE__`**
+An integer literal representing the presumed line number of the current
+source line within the current source file.
+[*Note 4*: The presumed line number can be changed by the `#line`
+directive [[cpp.line]]. — *end note*]
+- **`__STDC_EMBED_NOT_FOUND__, __STDC_EMBED_FOUND__, and __STDC_EMBED_EMPTY__`**
+The integer literals `0`, `1`, and `2`, respectively.
+[*Note 5*: These represent values replaced from
+\*has-embed-expression\*s [[cpp.cond]]. — *end note*]
 - **`__STDC_HOSTED__`**
 The integer literal `1` if the implementation is a hosted implementation
 or the integer literal `0` if it is a freestanding implementation
 An integer literal of type `std::size_t` whose value is the alignment
 guaranteed by a call to `operator new(std::size_t)` or
 `operator new[](std::size_t)`.
+[*Note 6*: Larger alignments will be passed to
 `operator new(std::size_t, std::align_val_t)`, etc.
 [[expr.new]]. — *end note*]
 - **`__STDCPP_FLOAT16_T__`**
 Defined as the integer literal `1` if and only if the implementation
+supports the ISO/IEC 60559 floating-point interchange format binary16 as
+an extended floating-point type [[basic.extended.fp]].
 - **`__STDCPP_FLOAT32_T__`**
 Defined as the integer literal `1` if and only if the implementation
+supports the ISO/IEC 60559 floating-point interchange format binary32 as
+an extended floating-point type.
 - **`__STDCPP_FLOAT64_T__`**
 Defined as the integer literal `1` if and only if the implementation
+supports the ISO/IEC 60559 floating-point interchange format binary64 as
+an extended floating-point type.
 - **`__STDCPP_FLOAT128_T__`**
 Defined as the integer literal `1` if and only if the implementation
+supports the ISO/IEC 60559 floating-point interchange format binary128
+as an extended floating-point type.
 - **`__STDCPP_BFLOAT16_T__`**
 Defined as the integer literal `1` if and only if the implementation
 supports an extended floating-point type with the properties of the
 | `__cpp_binary_literals`                 | `201304L` |
 | `__cpp_capture_star_this`               | `201603L` |
 | `__cpp_char8_t`                         | `202207L` |
 | `__cpp_concepts`                        | `202002L` |
 | `__cpp_conditional_explicit`            | `201806L` |
+| `__cpp_consteval`                       | `202211L` |
+| `__cpp_constexpr`                       | `202406L` |
 | `__cpp_constexpr_dynamic_alloc`         | `201907L` |
+| `__cpp_constexpr_exceptions`            | `202411L` |
 | `__cpp_constexpr_in_decltype`           | `201711L` |
+| `__cpp_constexpr_virtual_inheritance` | `202506L` |
 | `__cpp_constinit`                       | `201907L` |
+| `__cpp_contracts`                       | `202502L` |
 | `__cpp_decltype`                        | `200707L` |
 | `__cpp_decltype_auto`                   | `201304L` |
+| `__cpp_deduction_guides`                | `202207L` |
 | `__cpp_delegating_constructors`         | `200604L` |
+| `__cpp_deleted_function`                | `202403L` |
 | `__cpp_designated_initializers`         | `201707L` |
 | `__cpp_enumerator_attributes`           | `201411L` |
+| `__cpp_expansion_statements`            | `202506L` |
 | `__cpp_explicit_this_parameter`         | `202110L` |
 | `__cpp_fold_expressions`                | `201603L` |
 | `__cpp_generic_lambdas`                 | `201707L` |
 | `__cpp_guaranteed_copy_elision`         | `201606L` |
 | `__cpp_hex_float`                       | `201603L` |
 | `__cpp_if_consteval`                    | `202106L` |
 | `__cpp_if_constexpr`                    | `201606L` |
 | `__cpp_impl_coroutine`                  | `201902L` |
 | `__cpp_impl_destroying_delete`          | `201806L` |
+| `__cpp_impl_reflection`                 | `202506L` |
 | `__cpp_impl_three_way_comparison`       | `201907L` |
 | `__cpp_implicit_move`                   | `202207L` |
 | `__cpp_inheriting_constructors`         | `201511L` |
 | `__cpp_init_captures`                   | `201803L` |
 | `__cpp_initializer_lists`               | `200806L` |
 | `__cpp_namespace_attributes`            | `201411L` |
 | `__cpp_noexcept_function_type`          | `201510L` |
 | `__cpp_nontype_template_args`           | `201911L` |
 | `__cpp_nontype_template_parameter_auto` | `201606L` |
 | `__cpp_nsdmi`                           | `200809L` |
+| `__cpp_pack_indexing`                   | `202311L` |
+| `__cpp_placeholder_variables`           | `202306L` |
+| `__cpp_pp_embed`                        | `202502L` |
 | `__cpp_range_based_for`                 | `202211L` |
 | `__cpp_raw_strings`                     | `200710L` |
 | `__cpp_ref_qualifiers`                  | `200710L` |
 | `__cpp_return_type_deduction`           | `201304L` |
 | `__cpp_rvalue_references`               | `200610L` |
 | `__cpp_size_t_suffix`                   | `202011L` |
 | `__cpp_sized_deallocation`              | `201309L` |
+| `__cpp_static_assert`                   | `202306L` |
 | `__cpp_static_call_operator`            | `202207L` |
+| `__cpp_structured_bindings`             | `202411L` |
+| `__cpp_template_parameters`             | `202502L` |
 | `__cpp_template_template_args`          | `201611L` |
 | `__cpp_threadsafe_static_init`          | `200806L` |
+| `__cpp_trivial_relocatability`          | `202502L` |
+| `__cpp_trivial_union`                   | `202502L` |
 | `__cpp_unicode_characters`              | `200704L` |
 | `__cpp_unicode_literals`                | `200710L` |
 | `__cpp_user_defined_literals`           | `200809L` |
 | `__cpp_using_enum`                      | `201907L` |
 | `__cpp_variable_templates`              | `201304L` |
+| `__cpp_variadic_friend`                 | `202403L` |
 | `__cpp_variadic_templates`              | `200704L` |
 | `__cpp_variadic_using`                  | `201611L` |
 The following macro names are conditionally defined by the
 The values of the predefined macros (except for `__FILE__` and
 `__LINE__`) remain constant throughout the translation unit.
 If any of the pre-defined macro names in this subclause, or the
 identifier `defined`, is the subject of a `#define` or a `#undef`
+preprocessing directive, the program is ill-formed. Any other predefined
 macro names shall begin with a leading underscore followed by an
 uppercase letter or a second underscore.
 ## Pragma operator <a id="cpp.pragma.op">[[cpp.pragma.op]]</a>
 [basic.extended.fp]: basic.md#basic.extended.fp
 [cpp]: #cpp
 [cpp.concat]: #cpp.concat
 [cpp.cond]: #cpp.cond
 [cpp.cond.ha]: #cpp.cond.ha
+[cpp.embed]: #cpp.embed
+[cpp.embed.gen]: #cpp.embed.gen
+[cpp.embed.param]: #cpp.embed.param
+[cpp.embed.param.if.empty]: #cpp.embed.param.if.empty
+[cpp.embed.param.limit]: #cpp.embed.param.limit
+[cpp.embed.param.prefix]: #cpp.embed.param.prefix
+[cpp.embed.param.suffix]: #cpp.embed.param.suffix
 [cpp.error]: #cpp.error
 [cpp.import]: #cpp.import
 [cpp.include]: #cpp.include
 [cpp.line]: #cpp.line
 [cpp.module]: #cpp.module
 [cpp.rescan]: #cpp.rescan
 [cpp.scope]: #cpp.scope
 [cpp.stringize]: #cpp.stringize
 [cpp.subst]: #cpp.subst
 [cstdint.syn]: support.md#cstdint.syn
+[cstdio.syn]: input.md#cstdio.syn
+[dcl.attr]: dcl.md#dcl.attr
 [expr.const]: expr.md#expr.const
 [expr.new]: expr.md#expr.new
 [intro.compliance]: intro.md#intro.compliance
+[intro.compliance.general]: intro.md#intro.compliance.general
 [intro.multithread]: basic.md#intro.multithread
 [lex.ccon]: lex.md#lex.ccon
+[lex.charset]: lex.md#lex.charset
 [lex.digraph]: lex.md#lex.digraph
+[lex.header]: lex.md#lex.header
 [lex.key]: lex.md#lex.key
 [lex.name]: lex.md#lex.name
+[lex.name.special]: #lex.name.special
 [lex.phases]: lex.md#lex.phases
 [lex.token]: lex.md#lex.token
 [module.import]: module.md#module.import
 [support.limits]: support.md#support.limits
 [^3]: As indicated by the syntax, a preprocessing token cannot follow a
     `#else` or `#endif` directive before the terminating new-line
     character. However, comments can appear anywhere in a source file,
     including within a preprocessing directive.
+[^4]: Since, by macro-replacement time, all *character-literal*s and
     *string-literal*s are preprocessing tokens, not sequences possibly
     containing identifier-like subsequences (see [[lex.phases]],
     translation phases), they are never scanned for macro names or
     parameters.
+[^5]: An alternative token [[lex.digraph]] is not an identifier, even
     when its spelling consists entirely of letters and underscores.
     Therefore it is not possible to define a macro whose name is the
     same as that of an alternative token.
+[^6]: A *conditionally-supported-directive* is a preprocessing directive
     regardless of whether the implementation supports it.
+[^7]: Placemarker preprocessing tokens do not appear in the syntax
     because they are temporary entities that exist only within
     translation phase 4.

Diff to HTML by rtfpessoa