bartvandewoestyne / effective-modern-cpp

Sample code for the Effective Modern C++ book by Scott Meyers.

Effective Modern C++

I was an official reviewer for Scott Meyer his "Effective Modern C++" book. I have reviewed a large part of it (not all 42 items though). I accepted draft book material, reviewed the text, tested the code, and sent Scott comments and questions. In addition to testing almost all the code examples, I offered insights into the readability and comprehensibility of the descriptive material, and pointed out places where non-native English speakers (a significant part of the readership) might be confused or be unfamiliar with the vocabulary Scott had chosen.

This repository contains my compilable implementation for the code in the book. It is not officially linked to the book nor to Scott. It contains my personal, practical hands-on implementation of the sample code. My goal is to provide the C++ community with something that can be used in a hands-on way to play with the concepts explained in the book. Feel free to send me comments and questions, or to take a look at the TODO-list and send me pull-requests.

effective-modern-cpp's Issues

Setup Continuous Integration on Travis CI

We should setup Continuous Integration so we can easily test if everything works under several different environments. See https://travis-ci.org/

Support different compilers

This project should be compilable with as many C++11/14 compilers as possible. It should be easy to switch compilers. The buildsystem should be modified so that it is easy to build the project with one or the other compiler. I do not yet have a clear idea about how to approach this. Suggestions are definitely welcome.

Use Coverity Scan for static code analysis

Coverity Scan can be integrated in our Travis CI environment. See https://scan.coverity.com/travis_ci

Add Item 37-42.

I'm quite busy for the moment. If anybody has the time to add code for items 37 to 42, feel free!

Fix TODO's

There are still quite some TODO's spread throughout the different items. You can find them by grepping for TODO throughout the project. The more of these are fixed, the better! Feel free to send pull-requests.