creation of static during destruction

[Parapura Rajkumar]

hey all

class A
{

};
class B
{
~B()
{
static A a;
}
};

static B b;

Is this undefined behavior. or the standard seems to handle this case
as well ?

Thanks
Raja

[Rolf Magnus]

Parapura Rajkumar wrote:

hey all

class A
{

};
class B
{
~B()
{
static A a;
}
};

static B b;

Is this undefined behavior.

No. It's an error. B cannot be instantiated.

[Victor Bazarov]

Parapura Rajkumar wrote:

class A
{

};
class B
{
~B()
{
static A a;
}
};

static B b;

Is this undefined behavior. or the standard seems to handle this case
as well ?

I think it's unspecified.

The Standard (as I read it) says that the destruction of 'a' will
happen before B::~B returns (since it was constructed after 'b',
it has to be destroyed completely before 'b' is), however, it is known
that calling d-tors for static objects is done by registering them
with 'atexit' (although it is not explicitly specified by the Standard),
and the Standard does not specify what happens if you [try to] register
a function with 'atexit' while another function previously registered
with 'atexit' is executed during the program termination.

You might want to ask about it in comp.std.c++, refer to 3.6.3, 18.3,
6.7.

I say, try to avoid situations like that if possible.

V
--
Please remove capital 'A's when replying by e-mail
I do not respond to top-posted replies, please don't ask

[Parapura Rajkumar]

Rolf Magnus wrote:

Parapura Rajkumar wrote:

hey all

class A
{

};
class B
{
~B()
{
static A a;
}
};

static B b;

Is this undefined behavior.

No. It's an error. B cannot be instantiated.

Why is that.. i omitted the public to keep the post terse

[Victor Bazarov]

Rolf Magnus wrote:

Parapura Rajkumar wrote:

>hey all

class A
{

};
class B
{
~B()
{
static A a;
}
};

static B b;

Is this undefined behavior.

No. It's an error. B cannot be instantiated.

Oh, come on!

[Yahooooooooo]

Parapura Rajkumar wrote:

hey all

class A
{

};
class B
{
~B()
{
static A a;
}
};

static B b;

Is this undefined behavior. or the standard seems to handle this case
as well ?

Thanks
Raja

what is the use of this......B destructor will be called when B process
is complete...