4 ms·

We need less crap in the C++ standard, not more.

• gumby 8y ago
  I got to start a begin-with-an-empty-buffer project last year and chose c++17, treating it as a brand new language as if I'd never used C++ before. If you start with modern constructs and work backwards (i.e. ignoring legacy constructs and ideas that haven't aged well, like a "pure O-O" approach or iostreams) it's actually a pretty clear and expressive language. Another advantage with the 'empty buffer" is we could compile right away with almost every warning enabled (except for some 3P libraries we use) which also permitted the compiler to make some very aggressive optimizations. Unfortunately most people don't have this luxury :-(. But from this perspective I've generally been happy with the work the committee's been doing recently.
  • hasahmed 8y ago
    What resources did you use to learn the new features of C++. I don't know there language, but I began starting to learn it, and I don't know if what I'm learning is the nice new "modern constructs" or the crappy old ones.
    • pjmlp 8y ago
      Start with Tour of C++ from Bjarne, then follow up on CppCon and C++NOW session videos from Bjarne, Herb and Kate Gregory.
    • gumby 8y ago
      I can't stand videos so if you can't use pjmlp's advice, do start with the tour of c++, then read the summaries of standards compliance for gcc and llvm (which are on their respective websites) which will suggest which features are new and worth reading up on. I also read the standard (well, the "almost final" standard, which is actually the final one but which could be published on the net because it was what was voted on to become the standard -- the standards themselves are copyrighted and can't be posted to the net!) but unless you're used to reading language standards it may confused more than it answers. The blogs of folks like herb Sutter also explain a lot of subtle points and best practices.