C / C++ / MFC

struct TestStruct{    
CObject   obj[ 20 ];
};

// everything is on the stack
{
TestStruct ts; // TestStruct constructor and 20 CObject constructors called

} // TestStruct destructor and 20 CObject destructors called
// nothing to delete, no memory leak

{
// everything is on the heap, ts and with that 20 CObject's
TestStruct *ts = new TestStruct; // TestStruct constructor and 20 CObject constructors called

// everything is destroyed 20 CObjects's and ts
delete ts; // TestStruct destructor and 20 CObject destructors called
}

{
// everything is on the heap, ts and with that 20 CObject's
TestStruct *ts = new TestStruct;

// no delete
}
// memory leak

struct TestStruct{    
CObject   obj[ 20 ];
};

struct TestStruct{    
CObject*   pobj; //Pointer.
TestStruct()
{
 pObj = new CObject[20];
}
};

TestStruct obj; //Here the object is on stack. But all CObjects would in the heap.

~TestStruct()
{
 delete[] pObj;
}

Richard Andrew x64 wrote:

Are you saying that even though ts is created on the heap, that the CObject array inside the structure is created on the stack?

dehseth wrote:

p2 = p1;

dehseth wrote:

I read about shared pointers with templated which are not good for me to use right now?

• Use .NET - garbage collection means you don't need to worry about object ownership quite as much
• Use Objective C 2.0 - it allows garbage collection, and garbage collection means you don't need to worry about object ownership quite as much
• Use the Boehm allocator[^] - it's garbage collected, and garbage collection means you don't need to worry about object ownership quite as much
• As other posters have suggested, use Boost's shared_ptr class.