Beman Dawes <[EMAIL PROTECTED]> writes:
> The bigger issue is whether or not Boost should have a usual way of
> defining error exceptions thrown by Boost libraries
Probably not; std::exception works well enough.
> with raise() being one of the issues to be dealt with.
Definitely not. That's not a Boost-exception-specific issue.
> >and that boost libraries throw such exceptions *only* by calling
> >.raise(): i.e. never with a throw expression directly in the user
> >code.
>
> I'm not sure if what we need is a class, a concept, or just some
> documentation.
>
> But it does seem that individual Boosters have figured out
> (presumably better) ways to handle some aspects of reporting error
> exceptions. Would anyone be interested in trying to refine that
> vague feeling into something specific?
I don't know what the problem is yet.
--
David Abrahams
[EMAIL PROTECTED] * http://www.boost-consulting.com
Boost support, enhancements, training, and commercial distribution
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
