Re: Trouble with std::basic_ostringstream and libc++
Re: Trouble with std::basic_ostringstream and libc++
- Subject: Re: Trouble with std::basic_ostringstream and libc++
- From: Howard Hinnant <email@hidden>
- Date: Mon, 09 Jul 2012 12:16:16 -0400
On Jul 9, 2012, at 12:13 PM, Jesper Papmehl-Dufay wrote:
> I had forgotten about char16_t & char32_t. Yes, they are basically exactly what I would like to have. :) Unfortunately, Visual Studio is lagging behind Clang a bit when it comes to C++11 features, but hopefully it won’t be too long before we can move to char16_t.
I would be surprised if VS did not have wstring_convert and codecvt_utf8_utf16. These C++11 components were contributed to the standard by Dinkumware. Perhaps you can #ifdef in an unsigned short on VS to use with wstring_convert in the interim.
Howard
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden