Chapter 31. Using Objects to Prevent Memory Leaks

FAQ 31.01 When are memory leaks important?

FAQ 31.02 What is the easiest way to avoid memory leaks?

FAQ 31.03 What are the most important principles for resource management?

FAQ 31.04 Should the object that manages a resource also perform operations that may throw exceptions?

FAQ 31.05 Should an object manage two or more resources?

FAQ 31.06 What if an object has a pointer to an allocation and one of the object's member functions deletes the allocation?

FAQ 31.07 How should a pointer variable be handled after being passed to delete?

FAQ 31.08 What should be done with a pointer to an object that is allocated and deallocated in the same scope?

FAQ 31.09 How easy is it to implement reference counting with pointer semantics?

FAQ 31.10 Is reference counting with copy-on-write semantics hard to implement?

FAQ 31.11 How can reference counting be implemented with copy-on-write semantics for a hierarchy of classes?