Effective Modern C++ follows the proven guideline-based, example-driven format of Scott Meyers’ earlier books, but covers entirely new material. This book describes how to write effective software using C++11 and C++14—i.e. using modern C++.
This is a short document describing the preferred coding style for the Linux kernel. Coding style is very personal, and I won’t _force_ my views on anybody, but this is what goes for anything that I have to be able to maintain, and I’d prefer it for most other things too. Please at least consider the points made here.
This document is a result of a committee formed at Indian Hill to establish a common set of coding standards and recommendations for the Indian Hill community. The scope of this work is the coding style, not the functional organization of programs. The standards in this document are not specific to ESS programming only.
This source code is from Thinking in C++, 2nd Edition, Volume 2, by Bruce Eckel & Chuck Allison. You can use Borland, G++ (For version 3 and above only), Microsoft (For C++ with .NET only) to compile and build this source code. Writing perfect software may be a daunting task for developers, but a few defensive techniques which are routinely applied can go a long way toward narrowing the gap between code and ideal. Defensive programming practices are often used where high availability of the application is required, safety if utmost concern, or security is needed for application to work.
