[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Fix u32toutf8 so it encodes values > 0xFFFF correctly.

From: Eric Blake
Subject: Re: Fix u32toutf8 so it encodes values > 0xFFFF correctly.
Date: Wed, 22 Feb 2012 05:59:36 -0700
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.1) Gecko/20120209 Thunderbird/10.0.1

On 02/22/2012 05:19 AM, Linda Walsh wrote:
> Eric Blake wrote:
>> Not only can wchar_t can be either signed or unsigned, you also have to
>> worry about platforms where it is only 16 bits, such as cygwin; on the
>> other hand, wint_t is always 32 bits, but you still have the issue that
>> it can be either signed or unsigned.
> What platform uses unsigned wide ints?  Is that even posix compat?

Yes, it is posix compatible to have wint_t be unsigned.  Not only that,
but both glibc (32-bit wchar_t) and cygwin (16-bit wchar_t) use a 32-bit
unsigned int for wint_t.  Any code that expects WEOF to be less than 0
is broken.

Eric Blake   address@hidden    +1-919-301-3266
Libvirt virtualization library http://libvirt.org

Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]