2 ms·
The problem is that there are fewer qualified contributors that project authors would like. Every piece of code which is written and becomes used needs people t
by nine_k 5y ago
The problem is that there are fewer qualified contributors that project authors would like. Every piece of code which is written and becomes used needs people to contribute continued effort. Else the project dies, and the efforts put into it, and into depending on it, are wasted.
That said, I think that C++98 is a terrible language. I would understand targeting C++11. I would understand targeting the last version of OCaml which GCC4 can build. But the number of footguns C++98 introduces would make it for me a worse choice than plain C.
- pjmlp 5y agoAgreed, although some C++11 goodies like smart pointers, STL and RAII were already a thing in pre-C++98. Just because it is C++98, it isn't a recipe to write C with a C++ compiler.
- ncmncm 5y agoC++98 is less fun to code in than C++11, which is less fun than C++20. But with modern-style library support, C++98 can be quite safe and usable, at least single-threaded. But some things are unavoidably verbose. The only serious functional lack is moves, but that is a performance optimization. C++98 code can be upgraded to current whenever the perceived need to hang back dissipates. That said, implementing another compiler just for the sake of bootstrapping convenience would be powerfully silly: if you code a new Rust compiler, it should be the very best Rust compiler you can write, and better on at least some axes than the flagship one. Coding it in C++17 or 20 would be just good sense: Religion notwithstanding, C++ is a mature and powerful language well suited to the task. One real peculiarity of churn around bootstrapping is that, given good support for cross compilation, you hardly ever need to bootstrap at all. So if that is a thing that worries you, work supporting cross-compiling is your most productive course.