Re: Assertion vs Exception Handling

From:

James Kanze <james.kanze@gmail.com>

Newsgroups:

comp.lang.c++

Date:

Mon, 15 Mar 2010 15:41:44 -0700 (PDT)

Message-ID:

<03d215fe-7855-4b76-8763-217fb95758a5@15g2000yqi.googlegroups.com>

On Mar 14, 12:41 am, Ian Collins <ian-n...@hotmail.com> wrote:

On 03/14/10 12:26 PM, James Kanze wrote:

On Mar 12, 11:21 am, Ian Collins<ian-n...@hotmail.com> wrote:

On 03/12/10 11:36 PM, Leigh Johnston wrote:

"James Kanze"<james.ka...@gmail.com> wrote:

But most of the time, assertions will be active in released
code.

Sigh. What do you mean most of the time? We have been over
this before. By default assert does nothing in release mode
which is the way it should be. Release mode = NDEBUG = "not
debugging" = no op assert.

That depends how you define "release mode"

Most of the software I have released was released with
assertion on and most of the code I use (including my
preferred C++ compiler) has them enabled.

I'd rather have a bug report with a core file than one
without.

And I'd rather release the executables that I've tested, rather
than something else.

Did I say otherwise?

No. You didn't mention testing (although I know you're a firm
believer in it).

With regards to the core dump, there are some systems you can't
get it on. But an assertion failure will still occur closer to
the point of failure, and the error message will generally give
you some indication as to what when wrong.

--
James Kanze