simple question - constructors and destructors related 1

[DotNetGnat]

Guys,

let say I have a class A and I use the following two lines of code...

A a("ddd");

A* pa = new A("dsfd");

This is my understanding...The first one creates an object of class A and the second one creates an object of class A and returns a pointer reference...is that right...

when both of these objects go out of scope, does the destructor get called in both cases...or since I have used the new keyword in the second case...do I need to explicitly use delete keyword to deallocate the memory...

please shed some light on this issue...

thanks

-DNG

 

[Salem]

If you called new, then you need to call delete.
If you called new[], then you need delete[].



--
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.

 

[DotNetGnat]

thank you Salem...

So do I need to have delete in the destructor or in the same method where I have used new?? any sample code will be very helpful...

thanks

-DNG

 

[cpjust]

// This gets created on the stack, so when it does out of scope, the destructor is called and it disappears.
A a("blah");

// This gets created on the heap, and therefore continues to take up space in memory until YOU call delete on it. Once YOU call delete, the destructor is called and the memory is freed.
A* pA = new A("blah");

int main()
{
   A a("stack");
   A* pA = new A("heap");
   ...
   delete pA;
   return 0;
}

 

[DotNetGnat]

thanks cpjust...exactly this is the information I was looking for...

have star...

-DNG