Re: Encoding issues with literal strings (C++)

On 2006-12-22, Carlos Moreno <moreno_at_mochima_dot_com@xxxxxxxxxxxxxx> wrote:
jasen wrote:

[...]
Post something we can compile, and the full text of the warning,
and the full version number of the compiler you are using.

Thanks for your comments --- however, mabe your newsreader is now
showing the other replies in this thread, where John Fusco pointed
out the problem (the f that follows is being taken as part of the
hex sequence), and later found out that it is standard conforming
behaviour. (now *that*, I found odd :-))

yeah as is evident it's a new one to me.

It makes sense though.... the unicode character set has about 2^24 symbols
so C needs a way to represent them all...

It was (but no longer is) my understanding that after the \ only upto
three characters were interpreted as digits... (3 octal or x+2hex)


--

Bye.
Jasen
.

Relevant Pages