Bastian Blank wrote:
> On Tue, Aug 11, 2009 at 09:40:35PM +0200, Bernd Eckenfels wrote:
>> In article <[email protected]> you wrote:
>>> Not necessarily. Any sane implementation should just use wchar_t
>> Which could be UTF16 and therefore still has complicatd length semantics.
>
> No, wchar_t is UCS-4 (or UCS-2 in esoteric implementations like
> Windows).
No wchar_t is locale dependent (per POSIX).
BTW on gcc:
-fwide-exec-charset=charset
Set the wide execution character set, used for wide string and
character constants. The default is UTF-32 or UTF-16, whichever
corresponds to the width of wchar_t. As with -fexec-charset, charset can
be any encoding supported by the system's iconv library routine;
however, you will have problems with encodings that do not fit exactly
in wchar_t.
Note that default encoding is UTF-8, thus giving a UTF-32 wchar_t
in most developer machines.
ciao
cate
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
