The first edition of Effective C++ sold nearly 100,000 copies and was translated into four languages. It's easy to understand why. Scott Meyers' practical approach to C++ described the rules of thumb employed by the experts—the things they almost always do or almost always avoid doing—to produce clear, correct, efficient code.
Each of this book's 50 guidelines summarizes a way to write better C++, and the accompanying discussions are backed by specific examples. For this new edition, Meyers reworked every guideline in the book. The result is exceptional adherence to C++'s Draft International Standard, current compiler technology, and the latest insights into the use of C++ for real-world applications.
- Expert guidance on object-oriented design, class design, and the proper use of inheritance.
- An examination of the standard C++ library, including how the Standard Template Library and classes like string and vector affect the structure of well-written programs.
- Discussions of late-breaking language features like in-class constant initializations, namespaces, and member templates.
- Wisdom usually possessed by only the most experienced developers.
2. Shifting From C to C++.
Prefer iostream to stdio.h.
Prefer new and delete to malloc and free.
Prefer C++-style comments.
3. Memory Management.
Use delete on pointer members in destructors.
Be prepared for out-of-memory conditions.
Adhere to convention when writing operator new and operator delete.
Avoid hiding the "normal" form of new.
Write operator delete if you write operator new.
4. Constructors, Destructors, and Assignment Operators.
Prefer initialization to assignment in constructors.
List members in an initialization list in the order in which they are declared.
Make destructors virtual in base classes.
Have operator return a reference to *this.
Assign to all data members in operator.
Check for assignment to self in operator.
5. Classes and Functions: Design and Declaration.
Differentiate among member functions, non-member functions, and friend functions.
Avoid data members in the public interface.
Use const whenever possible.
Prefer pass-by-reference to pass-by-value.
Don't try to return a reference when you must return an object.
Choose carefully between function overloading and parameter defaulting.
Avoid overloading on a pointer and a numerical type.
Guard against potential ambiguity.
Explicitly disallow use of implicitly generated member functions you don't want.
Partition the global namespace.
6. Classes and Functions: Implementation.
Avoid member functions that return non-const pointers or references to members less accessible than themselves.
Never return a reference to a local object or to a dereferenced pointer initialized by new within the function.
Postpone variable definitions as long as possible.
Use inlining judiciously.
Minimize compilation dependencies between files.
7. Inheritance and Object-Oriented Design.
Differentiate between inheritance of interface and inheritance of implementation.
Never redefine an inherited nonvirtual function.
Never redefine an inherited default parameter value.
Avoid casts down the inheritance hierarchy.
Model "has-a" or "is-implemented-in-terms-of" through layering.
Differentiate between inheritance and templates.
Use private inheritance judiciously.
Use multiple inheritance judiciously.
Say what you mean; understand what you're saying.
Prefer compile-time and link-time errors to runtime errors.
Ensure that non-local static objects are initialized before they're used.
Pay attention to compiler warnings.
Familiarize yourself with the standard library.
Improve your understanding of C++.