Skip to content

Commit 9234447

Browse files
committed
[lex.phases] Use preprocessing token consistently
Prior to converting preprocessing tokens to tokens in phase 7, all tokens are strictly preprocessing tokens. Add the missing qualification is appropriate through the phases of translation up to that point of conversion.
1 parent 85de0af commit 9234447

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

source/lex.tex

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -170,14 +170,14 @@
170170
All preprocessing directives are then deleted.
171171

172172
\item
173-
For a sequence of two or more adjacent \grammarterm{string-literal} tokens,
173+
For a sequence of two or more adjacent \grammarterm{string-literal} preprocessing tokens,
174174
a common \grammarterm{encoding-prefix} is determined
175175
as specified in \ref{lex.string}.
176-
Each such \grammarterm{string-literal} token is then considered to have
176+
Each such \grammarterm{string-literal} preprocessing token is then considered to have
177177
that common \grammarterm{encoding-prefix}.
178178

179179
\item
180-
Adjacent \grammarterm{string-literal} tokens are concatenated\iref{lex.string}.
180+
Adjacent \grammarterm{string-literal} preprocessing tokens are concatenated\iref{lex.string}.
181181

182182
\item
183183
Each preprocessing token is converted into a token\iref{lex.token}.

0 commit comments

Comments
 (0)