3 ms·
> On the other hand, there aren't really any changes in 14 and 17 that break compatibility with code written in 11, at least that I'm aware of. auto_ptr has th
by gumby 7y ago
> On the other hand, there aren't really any changes in 14 and 17 that break compatibility with code written in 11, at least that I'm aware of.
auto_ptr has thankfully be removed, but if you have legacy code that uses it it won't compile under C++17. Of course if you have code that uses auto_ptr you should fix it, but realistically nobody has the time for that.
- ludamad 7y agoI mean, if tricky usage of auto_ptr is stopping you, you could probably use a drop-in replacement. But the 'and this adds to the sprint tasks how?' question still isn't answered in a good way
- TillE 7y agoYou could probably just find/replace unique_ptr. I'm pretty sure that's what I did a million years ago when auto_ptr was deprecated. C++17 does break some code by removing a few things, but they're pretty trivial and nothing sneaky.
- tjalfi 7y agoclang-tidy has a command to replace auto_ptr with unique_ptr[0]. I haven't used it in anger, though. [0] https://clang.llvm.org/extra/clang-tidy/checks/modernize-replace-auto-ptr.html https://clang.llvm.org/extra/clang-tidy/checks/modernize-rep...
- MauranKilom 7y agoDepends on how much it was used. But I was part of the effort to convert to C++17 for our (substantial) C++ code base of ~30 years and it was not painful at all.
- twoodfin 7y agoI also ran up against the deprecation of std::mem_fun and std::mem_fun_ref in a recent migration. Easy enough to replace with lambda expressions, but one more hurdle to running C++17 code.
- jcelerier 7y agoall compilers have ways to reinstate them to make porting easier, e.g. /D_HAS_AUTO_PTR_ETC=1 on msvc, -D_LIBCPP_ENABLE_CXX17_REMOVED_FEATURES=1 on clang...