Tag: Effective C++

2018
2018-01-02
Effective C++ item 48: Be Aware of Template Metaprogramming
2018-01-01
Effective C++ item 47: Use Traits Classes For Information About Types
2017
2017-12-27
Effective C++ item 46: Define Non-member Functions Inside Templates When Type Conversions Are Desired
2017-12-26
Effective C++ item 45: Use Member Function Templates to Accept "All Compatible Types"
2017-12-22
Effective C++ item 44: Factor Parameter-independent code Out of Templates
2017-12-21
Effective C++ item 43: Know How to Access Names in Templatized Base Classes
2017-12-17
Effective C++ item 42: Understand the Two Meanings of typename
2017-12-16
Effective C++ item 41: Understand implicit interfaces and compile-time polymorphism
2017-12-16
Effective C++ item 40: Use Multiple Inheritance Judiciously
2017-12-03
Effective C++ item 39: Use Private Inheritance Judiciously
2017-11-28
Effective C++ item 38: Model "has-a" or "is-implemented-in-terms-of" through composition
2017-11-25
Effective C++ item 37: Never Redefine a Function's Inherited Default Parameter Value
2017-11-25
Effective C++ item 36: Never Redefine an Inherited Non-virtual Function Value
2017-11-24
Effective C++ item 35: Consider Alternatives to Virtual Functions
2017-11-24
Effective C++ item 34: Differentiate Between Inheritance of Interface and Inheritance of Implementation
2017-11-19
Effective C++ item 33: Avoid Hiding Inherited Names
2017-11-19
Effective C++ item 32: Make Sure Public Inheritance Models "is-a"
2017-11-18
Effective C++ item 31: Minimize Compilation Dependencies Between Files
2017-11-18
Effective C++ item 30: Understand The Ins and Outs of Inlining
2017-11-15
Effective C++ item 29: Strive For Exception-safe Code
2017-11-12
Effective C++ item 28: Avoid Returning "handles" to Object Internals
2017-11-12
Effective C++ item 27: Minimize Casting
2017-11-12
Effective C++ item 26: Postpone Variable Definitions As Long As Possible
2012
2012-12-01
Effective C++ item 22: Declare data members private.
2012-12-01
Effective C++ item 21: Don't try to return a reference when you must return an object.
2012-12-01
Effective C++ item 20: Prefer pass-by-reference-to-const to pass-by-value.
2012-11-23
Effective C++ item 19: Treat class design as type design.
2012-11-23
Effective C++ item 18: Make interfaces easy to use correctly and hard to use incorrectly.
2012-07-29
Effective C++ item 17: Store newed objects in smart pointers in standalone statements.
2012-07-29
Effective C++ item 16: Use the same form in corresponding uses of new and delete.
2012-07-29
Effective C++ item 15: Provide access to raw resources in resource-managing classes.
2012-07-28
Effective C++ item 14: Think carefully about copying behavior in resource-managing classes.
2012-04-09
Effective C++ item 13: Use objects to manage resources.
2012-04-09
Effective C++ item 12: Copy all parts of an object.
2012-04-08
Effective C++ item 11: Handle assignment to self in operator=.
2012-04-07
Effective C++ item 10: Have assignment operators return a reference to *this.
2012-04-03
Effective C++ item 9: Never call virtual functions during construction or destruction.
2012-03-22
Effective C++ item 8: Prevent exceptions from leaving destructors.
2012-03-18
Effective C++ item 7: Declare destructors virtual in polymorphic base classes.
2012-03-18
Effective C++ item 6: Explicitly disallow the use of compiler-generated functions you do not want.
2012-02-21
Effective C++ item 5: Know what functions C++ silently writes and calls.
2012-01-22
Effective C++ item 4: Make sure that objects are initialized before they're used.
2012-01-20
Effective C++ item 3: Use const whenever possible
2012-01-17
Effective C++ item 2: Prefer consts, enums, and inlines to #defines.
2012-01-17
Effective C++ item 1: View C++ as a federation of languages.