Not quite. IMHO, it's better that os.c catches this UNICODE macro, and then uses MultiByteToWideChar and WideCharToMultiByte inside. The other way is to use an assert(FALSE) to prevent compilation using UNICODE, then the naive programmers like me will know something needs to be taken care of.
-Arthur ----- Original Message ----- I think you can see where I'm going with this. To fix the problem, I propose that for the functions listed above, os.c should always call the 'real' function name, and it should be the one ending with an 'A'. As it stands, the os.c has no ability to deal with wide characters, so there is no reason it should ever call the wide version of these Win32 functions. Thoughts? Regards, Rob Fowler --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
