|
Boost : |
From: William Kempf (sirwillard_at_[hidden])
Date: 2000-12-19 09:45:24
--- In boost_at_[hidden], "David Abrahams" <abrahams_at_m...> wrote:
>
> ----- Original Message -----
> From: "DEAN STURTEVANT" <dean_at_d...>
>
> > 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);
>
> This kind of interface is pretty much obsoleted by class instances
with
> virtual functions, isn't it?
IMHO, it's better obsoleted by the callback concept being
discussed ;). More flexible than a virtual override.
Bill Kempf
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk