Hi why would you use wstring anyway? On Sun, Apr 1, 2012 at 6:58 PM, Daniel Trebbien <dtrebbien@gmail.com> wrote:

Hello Michael,

Unfortunately, not yet. std::wstring support in BOOST_CHECK_EQUAL is Ticket #1136 (Let BOOST_CHECK_EQUAL support std::wstring): https://svn.boost.org/trac/boost/ticket/1136

Daniel Trebbien

On 2012-04-01, Michael Kochetkov <michael.kv@gmail.com> wrote:

...

Hello, Am I supposed to be able to use std::wstring in BOOST_CHECK_EQUAL? I.e. std::wstring s1,s2; BOOST_CHECK_EQUAL(s1,s2);

-- Michael Kochetkov

_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

Hi why would you use wstring anyway? I do not want to deal with iconv, icu or something like this (due to the cost of development, cost of QA, reliability, etc). So I use UCS2. It supports much more languages then ASCII (I do not care about the languages that do not fit in it), it is very simple. I use std::wstring just instead of std::string.

Yes, I know that gnu g++ and it's standard library and the boost have some problems with std::wstring but MS is really good with all that C++ quirks like wstring, wchar_t, wfstream, codecvt and etc. So my gcc builds just "narrow" strings on outputs and support English only. As far as the Windows is much larger market than anything else this approach suits me for many years. -- Michael Kochetkov

"Frank Birbacher" wrote in message news:jlqjeu$isg$1@dough.gmane.org...

Hmm, my impression has always been the other way round: With gcc you can use all sorts of locales and character encodings as you like. While with MS you are bound to some single system locale, you cannot even convert to UTF8 and interoperability with other systems is really hard.

Frank

Before saying that you cannot (easily) convert UTF-16 to UTF-8 on windows, you should have done your research: http://msdn.microsoft.com/en-us/library/windows/desktop/dd374130(v=vs.85).as... See the CP_UTF8 (CodePage). Since Vista, it is even Unicode 4.1 compliant and in any case, this function has been available since Windows 2000. Michael Goldshteyn