Question: Is it possible to preserve an object from garbagecollection (to live as long as the applet)? Answer: Yes, it is possible to preserve an object from garbage collection andlive
The canonical design of multithreaded applets is inherently flawed. You know what I’m talking about: the run method with the repaint/sleep statements embedded in a while(true). Any self-respecting operating systems
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
When an array of object is instantiated, the default constructor (and only the default constructor) of each member is invoked automatically. If you define no constructors at all, the compiler