C / C++ / MFC

Paresh Chitte wrote:

Initialise strData with NULL

Paresh Chitte wrote:

and check strData against NULL before deleting.

Nemanja Trifunovic wrote:

That's not necessary. Deleting NULL is guaranteed to be a no-op.

if (strData)
{
  delete [] strData;
  strData = NULL;
}

Paresh Chitte wrote:

if(NULL != strData)
{
delete[] strData;
}

if(NULL != strData)
{
  delete[] strData;
  strData = NULL;
}

Cedric Moonen wrote:

You should always always initialize your pointers to NULL.

<br />
CString* strData = new CString[count];<br />

<br />
vector<CString> strData;<br />

<br />
CStringArray strData;<br />

Nemanja Trifunovic wrote:

Unless you initialize them with something else

I.e., this is acceptable:


CString* strData = new CString[count];

Nemanja Trifunovic wrote:

In any case this new/delete construct is overused and leads to code that is not exception-safe and is hard to maintain. Wouldn't it be easier and safer to simply write something like:

CPallini wrote:

I don't blame for new/delete usage. You've to be disciplined though.

A* a = new A;
... // what if this trows?
B* b = new B;
... // what if this trows?
C* c = new C;
... // what if this trows?
delete c;
delete b;
delete a;

CPallini wrote:

BTW at the very end of your reasonment there's managed code!!

yudhisthira wrote:

Mac file format detected: please convert the source file to either DOS or UNIX format

yudhisthira wrote:

This is the only bug which is in my code

yudhisthira wrote:

How can i debug this

yudhisthira wrote:

Pls help me.

Rob Grainger wrote:

Incidentally, when you see a message number like "C4335", it's often worth typing into the Index page of MSDN Help (your local version, or online). This often displays a more detailed error message, as I used to resolve this issue.

Paresh Chitte wrote:

Pixel comparision would be helpful.