Instead of using #define macros to create a set of values, as in this (deprecated) example: #define JAN 1#define FEB 2//…#define DEC 12 Enum types are a significantly better choice:
Sometimes, an object must be converted into a built-in type (for instance, a string object passed as an argument to C function such as strcmp()) : //file Mystring.hclass Mystring {
When you instantiate an automatic object (e.g., on the stack) using its default constructor, mind that the correct syntax is: String str; //correct And not this: String str(); //entirely different
When designing a class hierarchy, you may face a decision between inheritance (aka IsA ) vs. containment (aka HasA) relation. For instance, if you are designing a Radio class, and
If a class may serve as a base class for others, its destructor should be virtual. This ensures RTTI support for objects of this class and objects derived from it,
When you have to “unconst” an object, as in this case: void print( unsigned char* c) { cout