Boost logo

Boost :

From: DEAN STURTEVANT (dean_at_[hidden])
Date: 2000-12-18 12:05:16

--- In boost_at_[hidden], "William Kempf" <sirwillard_at_m...> wrote:

> Depending on what assert we use, I'd agree ;). I like the
> about customizing assertion behavior. The "standard assert" in my
> (least) favorite compiler doesn't drop you into the debugger as
> nicely as other asserts (provided by the same company) do, for
> instance.

I agree wholeheartedly. Perhaps there should be a mechanism for the
client to provide a function for boost to call on assertion failures,
with a prototype something like:

typedef bool (*assertion_failure_fcn)(void* arg, const char* file,
unsigned line, const char* message);

The function would return true if the desired behavior is to continue
past the assertion, false if the system should abort.

The registration function might have prototype

void set_assertion_failure_fcn(assertion_failure_fcn f, void* arg);

Boost list run by bdawes at, gregod at, cpdaniel at, john at