Thinking in C++

From cleanup actions toward responsibility boundaries

Vol1 Chapter6 Initialization & Cleanup、Chapter13 Dynamic Object Creation；Vol2 Chapter1 Resource management / Exception safety、Chapter11 Concurrency

Volume 1 connects initialization and cleanup to the object lifetime, and Volume 2 then uses exceptions to examine whether this design really holds. Together they point out: when a function discovers failure, it does not need to know at the same time how the upper layer should recover; local objects can be responsible for cleanup, while the upper layer retains business decisions. But resource cleanup and state rollback are different; a container not leaking does not mean a modification has the strong guarantee. This site's examples use a local candidate configuration and a single commit to demonstrate this difference, rather than copying auto_ptr or handwritten byte containers. The original book's ZThread, dynamic exception specifications, and old function adapters belong to the historical background; volatile has never provided modern thread synchronization. The ideas of ownership, contracts, and separating changes should be retained, while correcting boundary errors in the examples that can be statically identified.