destructors for static and non static pointer-to-objects

[gorda]

Hello,

I have the following code, with a basic class having a constructor and
destructor. in the main section, I create a static pointer to the
class. My question is regarding the destructor. If I dont explicitly
delete the pointer, the destructor is called. However, I expected that
even with out explicitly deleting it, the destructor would be called
when the program ends.

#include <iostream>
using namespace std;

class basic
{
public:
basic()
{ cout << "constructor called" << endl; }

~basic()
{ cout << "destructor" << endl; }
};

int main()
{
static basic *bp = new basic;
//delete bp;
}

Output without the explicit delete call:
constructor

Output with the explicit delete call:
constructor
destructor
Can someone tell me why the destructor is not called when the pointer
is not explicitly deleted?

Thanks,
-Gorda Smith

[Ron Natalie]

"gorda" <sm*******@excite.com> wrote in message news:87**************************@posting.google.c om...

Can someone tell me why the destructor is not called when the pointer
is not explicitly deleted?

It's not supposed to. The fact that the pointer is destroyed doesn't mean
that the object it points to is. This is the way C++ is intended to work.

[Unforgiven]

gorda wrote:

Output without the explicit delete call:
constructor

Output with the explicit delete call:
constructor
destructor

A class is autodestructed only when it goes out of scope. Unfortunately,
only values that live on the stack or in the global data section of your
program will go out of scope; the former when the function they were created
in ends and the latter when the program ends.

In your example, the pointer lives on the stack, but your actual class
instance - as anything allocated by new - lives on the heap. The pointer
goes out of scope when main ends, but the class instance does not, hence the
destructor is called.

This is by design. Therefore, in C++, you *must* *always* have exactly as
many calls to delete as you do to new. Less calls to delete is a memory
leak.

--
Unforgiven

"Most people make generalisations"
Freek de Jonge

[Josephine Schafer]

"gorda" <sm*******@excite.com> wrote in message
news:87**************************@posting.google.c om...

Hello,

I have the following code, with a basic class having a constructor and
destructor. in the main section, I create a static pointer to the
class. My question is regarding the destructor. If I dont explicitly
delete the pointer, the destructor is called. However, I expected that
even with out explicitly deleting it, the destructor would be called
when the program ends.

A recent thread with 53 replies discussing this issue in detail -

http://groups.google.com/groups?dq=&...=3f56491e%240%
2423178%249a6e19ea%40news.newshosting.com&prev=/groups%3Fhl%3Den%26lr%3D%26i
e%3DUTF-8%26group%3Dcomp.lang.c%252B%252B

HTH.

[Kevin Goodsell]

gorda wrote:

Hello,

I have the following code, with a basic class having a constructor and
destructor. in the main section, I create a static pointer to the
class. My question is regarding the destructor. If I dont explicitly
delete the pointer, the destructor is called.
I doubt that, and your later statements contradict it.
However, I expected that
even with out explicitly deleting it, the destructor would be called
when the program ends.
Why would you expect that?

#include <iostream>
using namespace std;

class basic
{
public:
basic()
{ cout << "constructor called" << endl; }

~basic()
{ cout << "destructor" << endl; }
};

int main()
{
static basic *bp = new basic;
//delete bp;
}

Output without the explicit delete call:
constructor

Output with the explicit delete call:
constructor
destructor
Can someone tell me why the destructor is not called when the pointer
is not explicitly deleted?

Certainly, if you'll explain why you believe it should be. The behavior
you observe is the expected behavior (to all of us, at least).

-Kevin
--
My email address is valid, but changes periodically.
To contact me please use the address from a recent posting.