▲ | chris_wot 8 months ago | |||||||||||||||||||||||||
I think he has this about right. The project I contribute to (and no, I'm not a massive contributor) is LibreOffice and it is a C++ codebase. It has a decent build system that is easy for anyone to run out of the box. It uses modern C++17+ code, and though it has a lot of legacy code, it is being constantly modified by people like Noel Grandin via clang plugins (along with a lot of manual effort). This code was originally developed in the late 1980s. A good packaging tool would have helped a lot. | ||||||||||||||||||||||||||
▲ | umanwizard 7 months ago | parent | next [-] | |||||||||||||||||||||||||
I'm stoked to hear they're on C++17 now. When I contributed to LibreOffice (GSoC 2012) they were still on C++03 ! | ||||||||||||||||||||||||||
| ||||||||||||||||||||||||||
▲ | einpoklum 7 months ago | parent | prev [-] | |||||||||||||||||||||||||
> It uses modern C++17+ code Ha ha ha, that's funny. It uses pre-98 C++ code, that's set in stone because of extension/UNO APIs. Yes, you can use C++17 in a bunch of places, but not for the basic structures, classes, idioms etc. And - that's coming from a huge LibreOffice supporter. Speak at conventions, got the T-shirts, everything. | ||||||||||||||||||||||||||
|