Patch: New version of "UTF-16 to 'Win32 locale' conversions" and filenames (replacing convertion tables with Win32 API calls)

[João Garcia]

Andrew Haley wrote:

>The problem is that SWT maps *foo onto int.  So, many Java methods are
>passed ints, but there's no type checking -- all that you know is
>you're passed a pointer to something, and you pass that to a native
>method.  All the type checking we've grown to love has gone.
>  
>
I can see the merit of type checking. But is there any other reason for 
not to use the wrappers approach?

I have nothing against Mohan's C++ interface proposal. And I agree with 
most of Mohan's arguments up to this point. But I think it would be wise 
to keep windows and posix approaches to character convertion as close as 
possible. Character convertion is needed for many purposes. If this 
could be achived using C++, and without making the compiler's 
configuration too complex it, would be nice.

João

P.S.  UNICODE is not an encoding. Java uses UTF-16 encoding. Windows 
platform 2 (NT) also uses UTF-16 encoding. But windows platform 3 might 
use UTF-32 or UTF-64 encodings (I don't know)...