"modern" c++

Just say goodbye to your stupid niggerrunes and embrace the american alphabet already.

[code}//WONTFIX[/code]

>>60277868
OP specifically mentioned a laboratory so it's easy to assume that they need special scientific symbols and that you're a retard.

>>60277822
>> trying to compete with modern languages in terms of system programming, embedded systems etc.
Are you claiming it doesn't?
>> still no good support for unicode
What are you talking about? U"string" works fine.
>> ends up with fucking random bytes being written into the terminal
That is on you.

>>60277822
>lab
>programming scientists
the problem is you

>>60277909
utf8 is u8"string"
http://en.cppreference.com/w/cpp/language/string_literal

i know that if I std::cin>> and then std::cout it will be fine, but if I hardcode some special character into wstring, u8string etc. it doesn't work.

and maybe it works if you spend some time figuring out how to do it, but if you are some beginner and u want to just cout what you want to cout, its annoying

>>60278044
woah hold on.
that would require opie to have basic knowledge of the language

>>60277822
>Why doesn't c++ standard comitee make a support for unicode.
Basically, because natural language is hard and naive abstractions around it break down horribly. Any attempt to set in stone a standard library would be very likely to end in tears.

>>60278294
can you post the string you are trying to write and how you plan to print them?

>>60277822
how do i git gud in c++?
What books would you recomend?

>>60277822

I never had any problems.

- If I use UTF-8 in ordinary string literals, they always work -- even without using the u8 string prefix. You just need to have a code editor that supports UTF-8, like vim.

- I make sure that all data files use UTF-8 for strings. When I read them into char* strings, they're also UTF-8 internally.

- We've had UTF-8 support in <stdlib.h> going all the way back to C89: see mblen(), mbstowcs() and so forth. (Although I never had a need to use them, because it's so easy to just keep everything in UTF-8 strings everywhere, no need for conversions.)

I've worked extensively with UTF-8 strings in text files, data files, databases, network protocols, GUI, etc. for years and I have not had a single problem with it. The apps were fully internationalized, and we never advanced past C++98 and C99.

UTF-8 basically Just Works in C/C++.

>>60277822
>Why doesn't c++ standard comitee make a support for unicode.

Because C++ is based on C, and C originally had full support for UTF-8, and UTF-8 fully supports Unicode. Therefore, there was no need for C++ to do anything to support Unicode, because support was automatically there from the beginning.

In fact, that was the whole design goal of UTF-8 -- to give C immediate and automatic support for MBS (which is the generic category of encodings that Unicode belongs to), by ensuring compatibility with the char* data type.

>>60278523
>Basically, because natural language is hard and naive abstractions around it break down horribly. Any attempt to set in stone a standard library would be very likely to end in tears.

And yet, we have plenty of programming languages that offer full support for Unicode. The Unicode libraries for those languages are set in stone -- and somehow magically they were able to accomplish that feat without any tears. Amazing, isn't it?

>>60279455
C++ has unicode support.
Read the thread nigger.

>>60278294
never had issues with std::wstring
you can also use QString from Qt, its part of the Qt core so only 1 dll is needed for distribution.

Qt core also provides a lot of other utilities.

>>60278316
And yet all the string functions still operate on single byte characters. Not really what one can call unicode support.