> -----Original Message----- > From: Arthur Hsu [mailto:[EMAIL PROTECTED] > Sent: Friday, November 21, 2003 12:24 PM > To: [EMAIL PROTECTED] > Subject: Re: [sqlite] Win32 coders: change os.c? > > > 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. >
That's how we deal with this with the WinCE port of sqlite where we only have the Wide versions of the functions available, however to remain consistent with the single/multi byte filenames, etc. we use the Wide<->MultiByte. I concur with Arthur, I'd prefer the existing function names to be used. Chris --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
