This would lead to a more complex macro/function, but would, I think be
worth it.
[snip]
It would be a more complicated macro/function - but I agree with you, it
would be worth it.
This works nicely for the ANSI versions of the call, which return th ANSI
encoded string of bytes that is
Jeremy White wrote:
If we spend time on reworking some of the internals for Unicode is it
worth us considering the implications of 64bit further down the road?
I'd be very interested in starting to try to understand what 64bit
support would entail. I'm starting to put together a list of
Jeremy White wrote:
Seems like that should suffice, assuming that MSDN's definition of
character is a 32-bit UCS-2 character. I have no clue if MS
supports UCS-2 characters that use multiple 32-bit numbers to
represent a single character, but I believe such are legal. And if
they do support
3 matches
Mail list logo
