C / C++ / MFC

jblau wrote:

It was my understanding from the stuff I read that you should always have a DELETE for every NEW that you use.

Michael Dunn wrote:

Are you using normal or managed C++?

void LoadLists()
{
    Hashtable hashSelectedItems;
    ......(code working with the hashtable)
}

John R. Shaw wrote:

Do not allocate an object and delete an object in the same function, unless you have to

Gary R. Wheeler wrote:

Why?

class MyClass
{
   int n1,n2;
public:
   // member operations
   ......
};
// function using class
void MyFunc1()
{
   // this makes no since (sizeof(MyClass) is only 8 bytes)
   MyClass* mc = new MyClass;
   ......
   delete mc;
}
// function using class
void MyFunc2()
{
   // this makes more since
   MyClass mc;
   ......
}

Gary R. Wheeler wrote:

It's appropriate if you don't need the object for the entire life of the function.

void MyFunc()
{
   ......
   {
      MyClass mc;
      ......
   } // class is destoyed automatically here
   ......
}

jblau wrote:

illegal delete expression: managed type 'System::Collections::Hashtable' does not have a destructor defined