------- Comment #1 from jsm28 at gcc dot gnu dot org 2009-08-14 12:41 -------
This applies to both C and C++; the code in question is in libcpp.
Strictly, for C++ the compiler should act as if 'é' was replaced by
a UCN in phase 1 and so treat the second escape sequence like a valid
sequence \\u00E9 or one of the equivalent variants. This is unlikely
to be what the user wanted so it should probably be accompanied by a
warning while accepting the code. (This is in any case a separate
issue from the present bug report.)
--
jsm28 at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Component|c |preprocessor
Ever Confirmed|0 |1
Last reconfirmed|0000-00-00 00:00:00 |2009-08-14 12:41:24
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41067
