|
198 | 198 | contains exactly one \grammarterm{declarator-id}, which is the name
|
199 | 199 | declared by that \grammarterm{init-declarator} and hence one of the names
|
200 | 200 | declared by the declaration. The
|
201 |
| -\grammarterm{defining-type-specifiers}~(\ref{dcl.type}) in the |
| 201 | +\grammarterm{defining-type-specifier}{s}~(\ref{dcl.type}) in the |
202 | 202 | \grammarterm{decl-specifier-seq} and the recursive \grammarterm{declarator}
|
203 | 203 | structure of the \grammarterm{init-declarator} describe a
|
204 | 204 | type~(\ref{dcl.meaning}), which is then associated with the name being
|
|
1121 | 1121 | \grammarterm{type-specifier}{s} are discussed in the rest of this section.
|
1122 | 1122 | \end{note}
|
1123 | 1123 |
|
1124 |
| -\rSec3[dcl.type.cv]{The \grammarterm{cv-qualifiers}}% |
| 1124 | +\rSec3[dcl.type.cv]{The \grammarterm{cv-qualifier}{s}}% |
1125 | 1125 | \indextext{specifier!cv-qualifier}%
|
1126 | 1126 | \indextext{initialization!\idxcode{const}}%
|
1127 | 1127 | \indextext{type specifier!\idxcode{const}}%
|
1128 | 1128 | \indextext{type specifier!\idxcode{volatile}}
|
1129 | 1129 |
|
1130 | 1130 | \pnum
|
1131 |
| -There are two \grammarterm{cv-qualifiers}, \tcode{const} and |
| 1131 | +There are two \grammarterm{cv-qualifier}{s}, \tcode{const} and |
1132 | 1132 | \tcode{volatile}. Each \grammarterm{cv-qualifier} shall appear at most once in
|
1133 | 1133 | a \grammarterm{cv-qualifier-seq}. If a \grammarterm{cv-qualifier} appears in a
|
1134 | 1134 | \grammarterm{decl-specifier-seq}, the \grammarterm{init-declarator-list}
|
|
1357 | 1357 | \end{simpletypetable}
|
1358 | 1358 |
|
1359 | 1359 | \pnum
|
1360 |
| -When multiple \grammarterm{simple-type-specifiers} are allowed, they can be |
1361 |
| -freely intermixed with other \grammarterm{decl-specifiers} in any order. |
| 1360 | +When multiple \grammarterm{simple-type-specifier}{s} are allowed, they can be |
| 1361 | +freely intermixed with other \grammarterm{decl-specifier}{s} in any order. |
1362 | 1362 | \begin{note}
|
1363 | 1363 | It is \impldef{signedness of \tcode{char}} whether objects of \tcode{char} type are
|
1364 | 1364 | represented as signed or unsigned quantities. The \tcode{signed} specifier
|
|
2323 | 2323 | Because a \grammarterm{namespace-definition} contains
|
2324 | 2324 | \grammarterm{declaration}{s} in its \grammarterm{namespace-body} and a
|
2325 | 2325 | \grammarterm{namespace-definition} is itself a \grammarterm{declaration}, it
|
2326 |
| -follows that \grammarterm{namespace-definitions} can be nested. |
| 2326 | +follows that \grammarterm{namespace-definition}{s} can be nested. |
2327 | 2327 | \begin{example}
|
2328 | 2328 | \begin{codeblock}
|
2329 | 2329 | namespace Outer {
|
|
3699 | 3699 | \grammarterm{attribute}'s specification permits it. An \grammarterm{attribute} followed
|
3700 | 3700 | by an ellipsis is a pack expansion~(\ref{temp.variadic}).
|
3701 | 3701 | An \grammarterm{attribute-specifier} that contains no \grammarterm{attribute}{s} has no
|
3702 |
| -effect. The order in which the \grammarterm{attribute-tokens} appear in an |
| 3702 | +effect. The order in which the \grammarterm{attribute-token}{s} appear in an |
3703 | 3703 | \grammarterm{attribute-list} is not significant. If a
|
3704 | 3704 | keyword~(\ref{lex.key})
|
3705 | 3705 | or an alternative token~(\ref{lex.digraph}) that satisfies the syntactic requirements
|
|
0 commit comments