33 ms·
My company does a decent job at keeping up with the standard. Getting from C++11 to C++14 was challenging, and C++14 to C++17 took quite a bit of time, but we'
by veilrap 4y ago
My company does a decent job at keeping up with the standard. Getting from C++11 to C++14 was challenging, and C++14 to C++17 took quite a bit of time, but we're on track to be on C++20 later this year.
- rubyist5eva 4y agoDo you have a strategy for doing this? Since C++ stays relatively backwards compatible I would imagine there is lots of legacy code that gets untouched but newer features would go into the new stuff - with legacy code getting replaced only for big refactorings?
- veilrap 4y agoOur code tends to be shipped running on top of a relatively up-to-date version of linux. So we tend to go through the pain of testing/refactoring needed to get to the next version of C++ when we upgrade to the next stable version of linux that we're going to support.