Re: [boost] [general] What will string handling in C++ look like inthe future [was Always treat ... ]

Alexander Lamaison wrote:

By changing the OS-default encoding to assume char* string was UTF-8.

You keep talking about "OS-default encoding", but there's no such thing. POSIX operating systems do not assume anything about the encoding of char* (*). You have a global locale (**) in C/C++ programs, and the user can control it via environment variables (unless the program changes it), but the OS itself does not. (*) Except Mac OS X, which requires UTF-8 for paths. (**) Actually, you have two global locales - C and C++, not necessarily in sync with each other.