Created on 2011-12-03.00:00:00 last changed 148 months ago
Rationale (February, 2012):
This issue is a duplicate of issue 912.
The treatment of character literals containing universal-character-names is not clear. It is reasonable to conclude from 5.13.5 [lex.string] paragraph 15 that if a character named by a UCN cannot be represented by a single character in the runtime character set, it becomes a multibyte character and thus such a character literal is a multicharacter literal, with type int and an implementation-defined value. It would be nice if 5.13.3 [lex.ccon] had the complete story by itself or at least a reference to 5.13.5 [lex.string] for the details.
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2012-02-27 00:00:00 | admin | set | messages: + msg3851 |
| 2012-02-27 00:00:00 | admin | set | status: open -> dup |
| 2011-12-03 00:00:00 | admin | create | |