Re: [xml] The issue around LoadLibrary on Windows

There's no reason to use a macro, that's true. I don't see any 
indication that passed name argument is
UTF-8 encoded, so I don't see what's a justification of UTF-8 -> WCHAR 

If this is of any concern, LoadLibraryA interprets the 8-bit characters of 
the filename according to the user's codepage (character encoding) and
transforms it (internally in Windows) according to this codepage 
to UTF-16 and calls LoadLibraryW then.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]