2008/3/22, Oleh Derevenko <o...@eleks.lviv.ua>:

They are non-recoverable.

For an application with limited interactivity, like a game, you don't
need it. You design and tune everything so it always work (heh... you
wish).

For more interactivity you need to fail gracefully.

Ok, this is the only "recoverable" way, with the current asserts. But
only for an exception-enabled build. And exceptions are always slower
(although we can debate about efficiency when things fail...).

That's the only way to use current asserts.

How can you set the error code when all the handler gets is a string
describing the error?

Because I need them for an interactive physics environment, where the
user is supposed to play with all of ODE. I don't want it aborting,
throwing exceptions to C glue code (script language bindings in C). If
I have to write checks for everything (say, to catch every exception
and translate into proper error handling, hoping nothing inside ODE
leaks because of the throw), I seems more useful to have into the
core, so others can benefit.

--
Daniel K. O.
"The only way to succeed is to build success yourself"