Re:A proposal to start “llvm-libc” (2020)
by pjmlp on Wednesday December 08, 2021 @01:51AM
(#29481946)
Easy, C++ is more type safe than C since forever. Also the same reasoning why GCC has migrated to C++.
Microsoft has done the same with their new C runtime, and they have written a couple of blog posts exactly about that subject.
From "The Great C Runtime (CRT) Refactoring"
> So, as part of this great refactoring of the CRT, we have done an enormous amount of work to simplify and improve the quality of the code, so that it is easier to add features and fix bugs in the future. We have converted most of the CRT sources to compile as C++, enabling us to replace many ugly C idioms with simpler and more advanced C++ constructs. The publicly callable functions are still declared as C functions, of course (extern "C" in C++), so they can still be called from C. But internally we now take full advantage of the C++ language and its many useful features.
Microsoft has done the same with their new C runtime, and they have written a couple of blog posts exactly about that subject.
From "The Great C Runtime (CRT) Refactoring"
> So, as part of this great refactoring of the CRT, we have done an enormous amount of work to simplify and improve the quality of the code, so that it is easier to add features and fix bugs in the future. We have converted most of the CRT sources to compile as C++, enabling us to replace many ugly C idioms with simpler and more advanced C++ constructs. The publicly callable functions are still declared as C functions, of course (extern "C" in C++), so they can still be called from C. But internally we now take full advantage of the C++ language and its many useful features.
-- https://devblogs.microsoft.com/cppblog/the-great-c-runtime-c...
"C Runtime (CRT) Features, Fixes, and Breaking Changes in Visual Studio 14 CTP1"
https://devblogs.microsoft.com/cppblog/c-runtime-crt-feature...
"Introducing the Universal CRT"
https://devblogs.microsoft.com/cppblog/introducing-the-unive...