Re: Exception Misconceptions: Exceptions are for unrecoverable errors.

From:

peter koch <peter.koch.larsen@gmail.com>

Newsgroups:

comp.lang.c++

Date:

Thu, 24 Dec 2009 02:14:01 -0800 (PST)

Message-ID:

<70f4c8c9-4790-43ef-873d-b908c6e7ba3f@a21g2000yqc.googlegroups.com>

On 24 Dec., 00:51, Kaz Kylheku <kkylh...@gmail.com> wrote:

On 2009-12-23, Branimir Maksimovic <bm...@hotmail.com> wrote:

Kaz Kylheku wrote:

On 2009-12-22, Vladimir Jovic <vladasp...@gmail.com> wrote:

Stefan Ram wrote:
[snip]

  More elegantly? Actually, for correct and secure C++ code,
  all functions need to be written to be =BBexception safe=AB, but
  only a minority of C++ programmers does so or even is aware
  of it.

Why?

The above is false. Exception-safe code is needed to write code
that avoids resource leaks in the face of an exception.

For instance:

   {
      char *p = new char[256];
      f();
   }

hm , why would you do this?

To demonstrate one way in which code fails to be exception safe.

isnt't that
     {
        vector<char> p(256);
        f();
     }
is simpler?

This code no longer demonstrates a resource leak in the face of an except=

ion,

and so it would not have made a sutitable example to accompany my article=

Doh?

I guess what Branimir tried to tell was that you should always release
your ressources in a destructor. This gives you automatically the
basic exception guarantee.