asset ( condition ) vs try catch Block .......... which is better

[Pallav singh]

Hi

i seen code written using asset ( condition ) and try catch Block as
to Handle exception Condition ?
which one is better approach ?

when assert call terminate( ) .... does it clear all dynamic memory
allocated ?

Thanks
Pallav Singh

 

[Ian Collins]

Hi

i seen code written using asset ( condition ) and try catch Block as
to Handle exception Condition ?
which one is better approach ?

Assertions and exceptions serve different purposes. The former enforces
a contract, the latter indicated a (manageable) run time error.

when assert call terminate( ) .... does it clear all dynamic memory
allocated ?

If an application ends, how can it hold memory?

 

[Goran]

Hi

i seen code written using asset ( condition ) and try catch Block as
to Handle exception Condition ?
which one is better approach ?

Bad question. These are two very, very different things. First off,
assert is a macro that does nothing if not a debug build. Exception is
always thrown.

Also, assert will call abort, whereas exception from within a try/
catch will not (or at least, there has to be some other bug for that
to happen).

WRT memory: none have absolutely __nothing__ to do with memory
allocated by the rest of the code. That is to say, memory is not
deallocated just because assert fired, or because an exception is
thrown/caught.

However, depending on your runtime environment, memory might be given
back upon program termination. In particular, if we are talking about
modern desktop/server environments (operating systems), then yes,
memory will be given back to the system, but that has __absolutely__
nothing to do with assert, try/catch, or abort. That is because
operating system does that all by itself.

Goran.

 

[James Kanze]

Bad question. These are two very, very different things. First
off, assert is a macro that does nothing if not a debug build.

I'm not sure what you mean by "not a debug build". The assert
macro does nothing if NDEBUG is not defined when the header is
included; unless you define NDEBUG (and you almost never will),
the assert macro terminates your program if the condition isn't
true.

(About the only time you'd define NDEBUG is if the profiler says
you have to. And then, you'd normally only do so around the
critical function.