Title
Undefined behavior when creating an invalid string literal via stringizing
Status
open
Section
15.6.3 [cpp.stringize]
Submitter
US

Created on 2019-10-23.00:00:00 last changed 3 weeks ago

Messages

Date: 2023-01-15.00:00:00

Additional notes (January, 2023):

Forwarded to SG12 with paper issue 1409, by decision of the CWG and SG12 chairs.

Date: 2019-10-23.00:00:00

(From National Body comment US 142 on the C++20 DIS.)

Subclause 15.6.3 [cpp.stringize] paragraph 2 specifies:

If the replacement that results is not a valid character string literal, the behavior is undefined.

Undefined behavior during lexing is not acceptable. This ought to be ill-formed.

History
Date User Action Args
2023-01-05 08:22:04adminsetmessages: + msg7112
2019-10-23 00:00:00admincreate