Re: Unordered container of Glib::ustring

On 04/03/2013 06:30 PM, Paul Davis wrote:
    Why? Isn't it natural to wish to have a map containing user-defined
    strings, which may be in any language?

that describes std::string too.

all that Glib::ustring gives you are UTF-8-aware iterators.

It also uses UTF-8 *storage*, which makes your strings four times shorter (on Unix, twice shorter on Windows) if they are mostly-ASCII.

And it maps better with how Glib and Gtk work with strings (Unicode in UTF-8 instead of array-of-wchar_t).

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]