Created on 2014-09-09.00:00:00 last changed 49 months ago
[Moved to DR at the October, 2015 meeting.]
Proposed resolution (May, 2015):
Change 5.4 [lex.pptoken] bullet 3.3 as follows:
Otherwise, the next preprocessing token is the longest sequence of characters that could constitute a preprocessing token, even if that would cause further lexical analysis to fail.
Change 5.8 [lex.header] paragraph 1 as follows:
Header name preprocessing tokens
shallonly appear within a #include preprocessing directive ( 15.3 [cpp.include]). The sequences in both forms...
The “max munch” rule could be read to require the characters <int> in vector<int> to be parsed as a header-name rather than as three distinct tokens. 5.8 [lex.header] paragraph 1 says,
Header name preprocessing tokens shall only appear within a #include preprocessing directive (15.3 [cpp.include]).
However, that is not sufficiently clear that header-names are only to be recognized in that context.
|2017-02-06 00:00:00||admin||set||status: dr -> cd4|
|2015-11-10 00:00:00||admin||set||messages: + msg6063|
|2015-11-10 00:00:00||admin||set||status: ready -> dr|
|2015-05-25 00:00:00||admin||set||messages: + msg5443|
|2015-05-25 00:00:00||admin||set||status: drafting -> ready|