Re: Minimizing Dynamic Memory Allocation

And you miss the separation of responsibilities.
We have RAII/RIID/manager/etc classes -- that have responsibility to
manage a single resource. Examples: auto_ptr, string, vector, CFile,
CSingleLock, shared_ptr. They normally reside in libraries ready to
use. Ocasinally there is some some really new resource to cover, but
it is more like exceptional.

Then there are the normal user classes this whole discussion is about.
They, instead of attempting to manage resources directly shall use the
classes mentioned before. As members, base classes, locally, etc.
You do that, and need not write destructor (cctor, op= ) because
cleanup is properly done.

Most real-life problems come when a user class rather starts using raw
pointers or raw resources, obviously messing up somewhere the first 5+
times. And only to eventually discover using a manager class.

Care to point out what I miss? ;-)