Re: is such exception handling approach good?

From:

"Ben Voigt [C++ MVP]" <rbv@nospam.nospam>

Newsgroups:

microsoft.public.vc.language

Date:

Mon, 24 Dec 2007 12:36:51 -0600

Message-ID:

<OqCb#ulRIHA.3516@TK2MSFTNGP02.phx.gbl>

"George" <George@discussions.microsoft.com> wrote in message
news:0D39E682-644A-4308-A69F-1DB525BC950D@microsoft.com...

Hi Alex,

No, Stroustrup's idea is to throw wherever is appropriate to throw
(including the constructor, if necessary) to mainain well defined
state of an object.

I do not quite agree since I think if an exception is thrown from
constructor, I think it means the creation of the instance is not
successful
-- means not created at all. How could we maintain an instance into good
state if it is not created at all (exception thrown in constructor).

Please feel free to correct me if I am wrong.

You've explained why yourself -- the instance was not created at all,
therefore there is no instance with bad state.

regards,
George

"Alex Blekhman" wrote:

"George" wrote:

I have read the part and I think Bjarne's idea is to,

1. Keep the constructor small and try not to throw any exception
from
constructor;
2. Delay resource initialization into later steps to reduce the
possibility
to throw exception.

Is that correct understanding? Please feel free to correct me if
I am wrong.
:-)

No, Stroustrup's idea is to throw wherever is appropriate to throw
(including the constructor, if necessary) to mainain well defined
state of an object.

Alex