Re: [boost] [conversion] wchar_t support in lexical_cast

Alexei Alexandrov wrote:

But probably there are some caveats here. What are they?

Non-native wchar_t issues aside (I'm not sure of the rationale here), if the compiler is, as you say, new, then it should have an intrinsic wchar_t, and failure to get it working is either misconfiguration of the compiler (VC++, for example, needs a compiler switch to activate intrinsic wchar_t) or misconfiguration in the Boost config.hpp. Sebastian Redl