Re: Encoding issues with literal strings (C++)
- From: Carlos Moreno <moreno_at_mochima_dot_com@xxxxxxxxxxxxxx>
- Date: Sat, 23 Dec 2006 10:54:03 -0500
jasen wrote:
[...]
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)
Odd, isn't it? (that was exactly my understanding as well)
In comp.lang.c++.moderated, it was pointed out that C++ has universal
character codes --- after re-checking my copy of the ISO standard (the
1998 one), I see that my \xED could (should) have been \u00ED, and it
wouldn't suffer from the same problem, as the \u is followed by
*exactly* four hexadecimal digits (and there is also the \U which is
followed by exactly eight digits.
Thanks,
Carlos
--
.
- References:
- Encoding issues with literal strings (C++)
- From: Carlos Moreno
- Re: Encoding issues with literal strings (C++)
- From: jasen
- Re: Encoding issues with literal strings (C++)
- From: Carlos Moreno
- Re: Encoding issues with literal strings (C++)
- From: jasen
- Encoding issues with literal strings (C++)
- Prev by Date: Re: life expectancy of allocated resources in a .so file
- Next by Date: How to post a bug or suggestion easily?
- Previous by thread: Re: Encoding issues with literal strings (C++)
- Next by thread: coprocess question
- Index(es):
Relevant Pages
|
