3 ms·
This was 14 years ago. In that time * C++ has advanced considerably, and features like constexpr, lambas, unique_ptr, etc make writing code easier without runt
by RcouF1uZ4gsC 9y ago
This was 14 years ago. In that time
* C++ has advanced considerably, and features like constexpr, lambas, unique_ptr, etc make writing code easier without runtime overhead.
* The C Compiler that Linux uses, is now written in C++
* Clang tidy checks make it relatively easy to keep problematic C++ features out.
The fact that C++ is largely a superset of C means that just like GCC did, there can be a gradual migration of code.
- userbinator 9y agoC++ has advanced considerably ...and gained considerable complexity in the process. (I'm aware that C has gained some too, but not to the extent of C++.)
- mehrdadn 9y agoAnd I'd wager the Linux kernel has become more complex in the past couple decades too. But so what?
- okket 9y agoI'd argue: Yes, this is true. But you need at least on stable part in the toolchain for the kernel to get reliable results. You can't have your hammer transform to a screwdriver just because you swing it in the other direction. And if there is such a tool/case, you need to be absolutely sure how and when it behaves this way, on every possible platform. This is not the case for evolving C++.
- mehrdadn 9y agoTo me this situation is more more like having a screwdriver that can only be screwed with hammers from a particular manufacturer (Linux -> GCC), because that manufacturer is the only one that makes hammers with screw-driving tips that work with that particular screw head (non-portable macros for type-checking or whatever goes on there). You might as well just get a normal screwdriver (C++ compiler) and a normal screw (C++ program) like the rest of the world does -- and there's no implication that you have to keep changing screw tips (-std=c++??) every time Apple (standards committee) decides to come up with a new format (C++17).
- JdeBP 9y agoIf you are going to argue that, then you need to look again at the headlined item, where it was not the case that it behaved the same on every possible platform. It is a non-standard mechanism of one compiler, that was picked based upon a compromise decision about what versions even of that one compiler it would actually work with.
- ovao 9y agoIt's a true statement that C++ has gained considerable complexity since those days, largely due to the C++ committee's very religious approach to compatibility. How that added complexity has influenced how complex C++ applications must be is a discussion with considerably more nuance.
- netheril96 9y agoC language is simple, and the result is this considerably complex piece of implementation instead.
- iforgotpassword 9y agoThe problem is that you can't always require people to use the latest bleeding edge version to build your code. Especially the Linux kernel has quite some requirements for backwards compat. And yes, the fact that abi stability isn't really a thing in c++ land is a huge problem too. It has been tried before with beos and it sucked.