In article <36C### [at] geocitiescom> , "Jon A. Cruz" 
<jon### [at] geocitiescom> wrote:

> With wchar_t itself you get the same issue as with the float/double
> conversions  and int size. It's designated to contain Unicode characters, but
> may or may not be 16-bits. Some systems are reported to be using 32-bits for
> processor efficiency, so just imagine if I pass an array of 16-bit values to a
> C call expecting 32-bit values.
>
> So, that's why I start with wchar_t. If, however, no wide-char API calls are
> made, then USHORT should be no problem.

There are no C calls that expect it, wchar_t is a C++ keyword and there is
no standard C library that will expect or take it.


    Thorsten

Post a reply to this message