3 ms·
The goal is to be able to import that 20yo battle-tested library into your C++20 codebase and it just works.
by Maken 1y ago
The goal is to be able to import that 20yo battle-tested library into your C++20 codebase and it just works.
- feelamee 1y agothere are really a lot of simpler solutions than switching the standard of the whole codebase. E.g. write wrapper which interface doesn't require a new standard.
- reactordev 1y agoMmm pimpl’s and acne…
- anon-3988 1y agoHyrum law would dictate that your C++20 now becomes C++11 or whatever is the oldest in the whole chain of dependency.
- Maken 1y agoThat's kind of the point of C++'s retro-compatibility: C++20 contains new additions to the C++11 standard. Unless you rely in mistakes in the standard like auto_ptr or faulty atomics, which should be fixed regardless of the C++ standard, your C++11 dependencies are perfectly valid C++20 and do not block the new shiny toys.