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

[Mohan Embar]

Hi Andrew,

> > But is there anyway around this, given that you're forced to use
> > JNI outside of the gcj world? The thing that dazzled me about the
> > SWT OS wrapper approach is that I can step through my OS calls
> > directly in the Java debugger.
>
>That's why they did it, yes.  But it would have been possible to keep
>type safety by putting the native pointers into container classes, at
>some cost in efficiency.  And memcpy() is best kept well away from
>Java, IMO.

Good points. I never thought about a type-safe container class for
pointers.

> > I understand that there's a loss of type safety with some of the
> > mappings, but when I compare that to the hell I had to go through
> > trying to convince MS Visual Studio to fire up an instance of IBM
> > Visual Age in order to debug my JNI DLL, I was dancing on the
> > tables when I read about that approach.
>
>Well, I don't know about that.  I used gdb, which wasn't perfect but
>would debug the SWT bindings -- I could even step from Java through
>gtk callbacks.

Okay: first convince my project manager to replace MS Visual Studio
with gcc and then we'll talk.... :)

-- Mohan
http://www.thisiscool.com/
http://www.animalsong.org/