7 ms·
In my experience you stick with a certain version, even as new stuff comes up. My current work is in C++14 and will not move to newer versions.
by bad_alloc 8y ago
In my experience you stick with a certain version, even as new stuff comes up. My current work is in C++14 and will not move to newer versions.
- therockhead 8y agoWhat are the reasons for not moving? We are currently on C++ 17 and we need to support Windows, macOS,iOS and android.
- gmueckl 8y agoOne reason: consistency. When you introduce new features, idioms shift and maintaining code that uses multiple idioms for similar purposes is simply less fun. In the worst case you make changes harder because you now have to make your changes compatible with more modes of usage.
- ryl00 8y agoAn IT department that controls compiler upgrades, in my case :/. We're still stuck on not-quite-C++11 because we're still stuck on g++-4.3
- gpderetta 8y agoDependency (sometimes even binary dependency) with a library that doesn't support newer standard can be an issue. Not all compilers guarantee interoperability, and even with those that do there can be bugs.
- gpderetta 8y agoNo plans to move ever, or just sticking to it for a while? The latter is perfectly reasonable, the former seems a great way to end up with technical debt: at some point compilers might (although it is admittedly very unlikely at least for gcc) drop support for older standards, 3rd party libraries as well(this is much more likely).