Smart Pointers and RAII

Managing resources by hand (new/delete, fopen/fclose, lock/unlock) is the source of C++ programmers' nightmares. The RAII principle tells us: bind acquiring a resource to an object's construction, hand releasing it to the destructor, and let the scope manage the lifetime for you. In this chapter we first build a deep understanding of RAII, then set up the "ownership" model—exclusive, shared, and borrowed, each in its rightful place—then walk through the design philosophy and correct usage of unique_ptr, shared_ptr, and weak_ptr one by one, and finally see how custom deleters and scope_guard handle more complex resource scenarios.

Chapter Contents

STARTFINISHDeep Dive into RAII: The Cornerstone of Resource Management→STARTFINISHResource Ownership: Exclusive, Shared, and Borrowed→STARTFINISHDeep Dive into unique_ptr: The Zero-Overhead Smart Pointer with Exclusive Ownership→STARTFINISHDeep Dive into shared_ptr: Shared Ownership and Reference Counting→STARTFINISHweak_ptr and Circular References→STARTFINISHCustom Deleters and Intrusive Reference Counting→STARTFINISHscope_guard and defer: A General-Purpose Scope Guard→STARTFINISHThe PIMPL Idiom: unique_ptr, shared_ptr, and Incomplete Types→