https://gcc.gnu.org/bugzilla/show_bug.cgi?id=33167
--- Comment #7 from joseph at codesourcery dot com ---
"longest sequence of characters that can constitute the escape sequence"
resolves an ambiguity between alternative parses permitted by the syntax;
it doesn't need to deal with anything that
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=33167
--- Comment #6 from Albert Chan ---
if gcc hex escape AND octal is right, does it contradict comment #1 ?
"octal or hexadecimal ... longest sequence that constitute escape sequence"
I noticed OLD python (2.0) also use the C rule regarding hex e
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=33167
--- Comment #5 from joseph at codesourcery dot com ---
The standard syntax production for octal-escape-sequence (C11 6.4.4.4#1)
only allows one, two or three digits.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=33167
Albert Chan changed:
What|Removed |Added
CC||albertmcchan at yahoo dot com
--- Comment
--- Comment #3 from raeburn at raeburn dot org 2007-08-24 19:45 ---
(In reply to comment #2)
> Yep, looks like you are right from the standard. That sucks then. I wish it
> were the other way because I don't see a way to enter a literal single
> character in hex followed a by single cha
--- Comment #2 from weston at computer dot org 2007-08-24 16:04 ---
Yep, looks like you are right from the standard. That sucks then. I wish it
were the other way because I don't see a way to enter a literal single
character in hex followed a by single character [A-Z0-9] without escape
--- Comment #1 from pinskia at gcc dot gnu dot org 2007-08-23 21:59 ---
No GCC is correct.
The standard says:
Each octal or hexadecimal escape sequence is the longest sequence of characters
that can constitute the escape sequence.
So that means the B is going to be taken and be used for
