We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
... or a misunderstanding on my part ?
From string "\x0CTUV", the compiler generates 0x0C 0x55 0x56 0x57 0x00
From string "\x0CABC", the compiler generates 0xCA 0x42 0x43 0x00 ... rather than the expected 0x0C 0x41 0x42 0x43 0x00
I thought the \x escape sequence in a string instructed the compiler to encode the very next two characters as a hexadecimal byte.
Am I missing something ?
"Each octal or hexadecimal escape sequence is the longest sequence of characters that can constitute the escape sequence."
But even so, at least in C99 an octal sequence can't be longer than three digits. So if you actually write down a three-character octal sequence, the result is unambiguous.
The difference is not in the text, but in the grammar rules (which are implied by the "can constitute" clause in the above). An octal escape sequence is a '\' followed by one to three octal digits, a hex escape sequence is a '\x' followed by at least one hex digit.