News for hackers. Stuff that matters.
Re:Writing Good C++14 by Default [pdf] by tmaly on Wednesday September 23, 2015 @07:39AM (#10264406)
maintaining the legacy code written in the late 90s is the hardest part. It would be great if we could just press a button and the old code is now magically C++14
Re:Writing Good C++14 by Default [pdf] by neuromancer2701 on Wednesday September 23, 2015 @09:10AM (#10264769)
My problem is that I work with a bunch of 90s era engineers and they still want to code that way. It is what they know and they don't want to spend the time to learn any of that new fangled C++11. Most of them are 5-10 years from retirement if not working a shorten week already so why waste their time.
Re:Writing Good C++14 by Default [pdf] by lorenzhs on Wednesday September 23, 2015 @11:12AM (#10265495)
I haven't actually tried it, but clang's C++ Modernizer tries to automate some of the boring manual tasks in bringing old code up to speed (such as using nullptr instead of NULL or 0, or more the for(T x : c) loop construct). See http://clang.llvm.org/extra/clang-modernize.html (integrated into clang-tidy now)