Re: Assertion vs Exception Handling

From:

James Kanze <james.kanze@gmail.com>

Newsgroups:

comp.lang.c++

Date:

Sat, 13 Mar 2010 15:26:20 -0800 (PST)

Message-ID:

<742486ea-ea49-4138-9cfb-db24f706600b@q21g2000yqm.googlegroups.com>

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. (One recent but I had to track down was
due to the fact that VC++ doesn't always call destructors when
optimization is turned on---in the Visual IDE's "release mode".
And that in the code in question, smart pointers were an
appropriate solution, and were being used.)

--
James Kanze