Closed wg21bot closed 4 years ago
SG12 guidance for all "undefined behavior in the preprocessor" NB comments:
Reject; but create issues to track them.
SF | F | N | A | SA |
---|---|---|---|---|
6 | 3 | 1 | 0 | 0 |
Does EWG want to consider any of the “Undefined Behavior in the preprocessor” comments for C++20?
F | A |
---|---|
0 | 9 |
No consensus for change. Resolution: create issues to track them.
Rejected. There was no consensus to adopt this change at this time.
Undefined behavior lexing and tokenizing the program text has no place in a modern standard. Unnecessary undefined behaviour in our standard raises a wide variety of concerns, not least with the security community, and all concerns related to turning source code into tokens for subsequent analysis should be either diagnosable errors, or (conditionally) supported behavior. This comment is a principle statement for more detailed comments that follow, and as a catch-all for any further occurrences that were missed.
Proposed change: Remove Undefined Behavior lexing and tokenizing the program text.