Hi Steven, 2010/10/4 Steven McCoy <[email protected]>: > Native wide character support is complicated, > MSVC forwards on _NATIVE_WCHAR_T_DEFINED > but without the conversion APIs data structures > that have defined WCHAR member variables are unusable? > I need a multi-byte string value of MIB_IFROW::wszName.
I believe, building with or without wchar_t as a native type has nothing to do with ability to use the conversion APIs. It's just a matter of how wchar_t is defined by MSVC: "non-native" wchar_t means it's just #defined to unsigned short, "native" means that wchar_t is a separate type. Regards, Ivan > 2010/9/23 Mikael Helbo Kjær <[email protected]> >> >> I was unable to make compatible OpenPGM DLLs for my stuff (I needed them >> without buffer security and without wchar_t as a native type to be >> compatible with Qt). >> > > Security enhanced CRT usage is now configurable with > CONFIG_HAVE_SECURITY_ENHANCED_CRT. > Native wide character support is complicated, MSVC forwards > on _NATIVE_WCHAR_T_DEFINED but without the conversion APIs data structures > that have defined WCHAR member variables are unusable? > I need a multi-byte string value of MIB_IFROW::wszName. > http://msdn.microsoft.com/en-us/library/aa366836(VS.85).aspx > -- > Steve-o > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > > _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
