Created on 2024-03-09.00:00:00 last changed 4 months ago
Proposed resolution (approved by CWG 2024-05-17):
Change in 5.13.5 [lex.string] paragraph 7 as follows:
The common encoding-prefix for a sequence of adjacent string-literals is determined pairwise as follows: If two string-literals have the same encoding-prefix , the common encoding-prefix is that encoding-prefix . If one string-literal has no encoding-prefix , the common encoding-prefix is that of the other string-literal. Any other combinations are ill-formed.
The string-literals in any sequence of adjacent string-literals shall have at most one unique encoding-prefix among them. The common encoding-prefix of the sequence is that encoding-prefix, if any.
CWG 2024-05-03
CWG preferred a holistic instead of a pairwise approach.
[Accepted as a DR at the June, 2024 meeting.]
(From submission #511.)
Subclause 5.13.5 [lex.string] paragraph 7 does not properly handle the case where both encoding-prefixes are absent:
The common encoding-prefix for a sequence of adjacent string-literals is determined pairwise as follows: If two string-literals have the same encoding-prefix , the common encoding-prefix is that encoding-prefix . If one string-literal has no encoding-prefix , the common encoding-prefix is that of the other string-literal. Any other combinations are ill-formed.
Possible resolution [SUPERSEDED]:
Change in 5.13.5 [lex.string] paragraph 7 as follows:
The common encoding-prefix for a sequence of adjacent string-literals is determined pairwise as follows:If two string-literals have the same encoding-prefix, the common encoding-prefix is that encoding-prefix.If one string-literal has no encoding-prefix, the common encoding-prefix is that of the other string-literal or is absent if the other string-literal has no encoding-prefix. Otherwise, both string-literals shall have the same encoding-prefix, and the common encoding-prefix is that encoding-prefix.Any other combinations are ill-formed.
History | |||
---|---|---|---|
Date | User | Action | Args |
2024-07-20 13:52:34 | admin | set | status: ready -> dr |
2024-06-27 04:25:11 | admin | set | status: tentatively ready -> ready |
2024-05-17 22:24:28 | admin | set | status: review -> tentatively ready |
2024-05-09 06:27:48 | admin | set | messages: + msg7693 |
2024-05-09 06:27:48 | admin | set | messages: + msg7692 |
2024-05-09 06:27:48 | admin | set | status: open -> review |
2024-03-09 00:00:00 | admin | create |