ctor throws an exception case

[puzzlecracker]

When ctor throws an exception, dtor is not called for that object
(correct me if I am wrong) - then how would already allocated memebers
de-allocated?

Thanks.

[peter koch]

puzzlecracker skrev:

When ctor throws an exception, dtor is not called for that object
(correct me if I am wrong) - then how would already allocated memebers
de-allocated?

Thanks.

Is that not in the faq? Because every object constructed will be
destructed when unwinding:

class A
{
....
}
class B
{
....
}
class D: B
{
A a;
D() {throw;}
}

Above B::~B and A::~A will both be called (assuming A and B's
constructor does not throw).

/Peter

[Alf P. Steinbach]

* puzzlecracker:

When ctor throws an exception, dtor is not called for that object
(correct me if I am wrong) - then how would already allocated memebers
de-allocated?

Please ask in [comp.lang.c++.moderated] right away, if you haven't already.

--
A: Because it messes up the order in which people normally read text.
Q: Why is it such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?

[Andre Kostur]

On Wed, 10 May 2006 15:17:57 -0700, puzzlecracker wrote:

When ctor throws an exception, dtor is not called for that object
(correct me if I am wrong) - then how would already allocated memebers
de-allocated?

Correct. If an exception propogates out of a ctor, the dtor for that
object will not be invoked as that object had not completed construction.
Any member variables of that object that had ben completely constructed
will be destroyed in the reverse order that they were constructed in (as
normal).

Note that the destructor of a pointer-to-object doesn't do anything...
that's what std::auto_ptr (and other relatives of it) are for.

[puzzlecracker]

Please ask in [comp.lang.c++.moderated] right away, if you haven't already.

Why? are you not qualified to answer it?

[peter koch]

Alf P. Steinbach skrev:

* puzzlecracker:

When ctor throws an exception, dtor is not called for that object
(correct me if I am wrong) - then how would already allocated memebers
de-allocated?
Please ask in [comp.lang.c++.moderated] right away, if you haven't already.

Ouch! So he already asked there? I had some kind of a dejá vù
experience, but a quick check did not show anything.

/Peter --
A: Because it messes up the order in which people normally read text.
Q: Why is it such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?

[Diego Martins]

puzzlecracker wrote:

Please ask in [comp.lang.c++.moderated] right away, if you haven't already.

Why? are you not qualified to answer it?

he clearly called you a cross-poster. I am sure you got that!

dissimulation is futile :(