Re: Exception handling Organization: unknown

From:

"Bo Persson" <bop@gmb.dk>

Newsgroups:

comp.lang.c++.moderated

Date:

Tue, 22 Sep 2009 19:24:12 CST

Message-ID:

<7hskaaF2vf5q6U1@mid.individual.net>

George Neuner wrote:

On Mon, 21 Sep 2009 17:07:29 CST, "Bo Persson" <bop@gmb.dk> wrote:

Alan McKenney wrote:

We've tried using exceptions a little, but have ended
up ripping out exceptions in the few places we used them.

The problems I see are:

1. Expense. You can't use exceptions unless you can be
    quite sure that they will occur rarely. I work with
    real-time data, so if too many exceptions are thrown,
    we lose data.

Exceptions are supposed to be used for exceptional conditions. :-)

And that makes their [lack of] performance a potential problem for
embedded programming where "exceptional conditions" due to
uncontrollable environments can be expected to happen fairly often.

Here we are down to definitions. :-)

If something is expected to happen fairly often, it is not
exceptional. Then you should probably not use exceptions for such
cases, but instead test for one of a set of expected conditions that
you must be prepared to handle.

For example, FileOpen should probably not throw an exception for
file-not-found, but might throw for disk full or network connection
lost.

Bo Persson

--
[ See http://www.gotw.ca/resources/clcm.htm for info about ]
[ comp.lang.c++.moderated. First time posters: Do this! ]