By: Minuous
That's incorrect, UNIX is not even mentioned in the official C standard.
By: runciblebatleth
In reply to <a href="https://www.osnews.com/story/140142/some-sanity-for-c-and-c-development-on-windows/#comment-10441318">Minuous</a>.
C and Unix were born as twins. Any C implementation that differs from Unix is wrong by definition.
By: sukru
In reply to <a href="https://www.osnews.com/story/140142/some-sanity-for-c-and-c-development-on-windows/#comment-10441318">Minuous</a>.
The article is too focused on the standard C++ library and lack of utf-8 as default.
However if you use the modern C++/WinRT (derived from C++/CLI), there are simple tools to move between those worlds:
https://devblogs.microsoft.com/oldnewthing/20210922-00/
Basically most programs would not care what their strings internally contain (as long as the character set is representable). However the care needs to be done at the I/O boundaries.
Am I receiving a utf-8 request from HTTP?
Will I write this file as ASCII or utf-16?
Does the Remote Procedure Call require any conversions?
Inside those boundaries, once again, you are free to stick with "std::string" or "std::wstring" without care.
By: Minuous
The linked article is silly, he just blames Windows for every difference between Windows and UNIX, it is just as plausible if not more so that UNIX is the outlier. (Eg, AmigaOS works much the same as Windows as far as the aspects mentioned in the article are concerned,) The Unicode he complains about can be enabled if it is wanted but changing the default would be unwise; I certainly would not want it for my own programs,