News for hackers. Stuff that matters.
Re:We have C++14 by eropple on Monday August 18, 2014 @11:01PM (#8195870)
> "Modern C++" doesn't exist outside of blog posts, books, and tutorials.

That you aren't used to doing greenfield development doesn't mean others are likewise impaired.

Re:We have C++14 by stinos on Tuesday August 19, 2014 @03:02AM (#8196265)
While a bit harsh sounding, this is actually spot on. What I write nowadays vs 5 years ago: hard to believe it is the same laguage.
Re:We have C++14 by eropple on Tuesday August 19, 2014 @09:32AM (#8197150)
Exactly. I only write greenfield C++ and I dig it a whole bunch.
Re:We have C++14 by p0nce on Tuesday August 19, 2014 @10:05AM (#8197312)
Good for you. It would be harder to dig if you had to do some maintenance like less lucky lifeforms.
Re:We have C++14 by gurkendoktor on Tuesday August 19, 2014 @03:26PM (#8199261)
I have only worked on one legacy C++ code base, and it was a student job, but I've enjoyed it a lot. Most of "modern C++" can be applied to an old code base step by step, all the way up from C with classes. As long as nobody decides to introduce the project's first "const" somewhere in a core class... :)
Re:We have C++14 by eropple on Tuesday August 19, 2014 @11:54AM (#8197994)
I hope you didn't take that to mean that I don't maintain my own code. But I can choose when to refactor and when to put up with it. C++ isn't a tool to use when you can't own the project.