Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
A continuation on C++ and UTF8 – Why not just replace ASCII?
Why is there no std::ustring which could replace both std::string, std::wstring in new applications?
Of course with corresponding support in the standard library. Similarly to how boost::filesystem3::path doesn’t care about string representation and works with both std::string and std::wstring.
Why would you replace anything?
stringandwstringare the string classes corresponding tocharandwchar_t, which in the context of interfacing with the environment are meant to carry data encoded in, respectively, “the system’s narrow-multibyte representation” and fixed-width in “the system’s encoding”.On the other hand,
u8/u/U, as well aschar16_tandchar32_t, as well as the corresponding string classes, are intended for the storage of Unicode codepoint sequences encoded in UTF-8/16/32.The latter is a separate problem domain from the former. The standard doesn’t contain a mechanism to bridge the two domains (and a library such as
iconv()is typically required to make this bridge portable, e.g. by transcoding WCHAR_T/UTF-32).Here’s my standard list of related questions: #1, #2, #3