Boost logo

Boost :

From: David Bergman (davidb_at_[hidden])
Date: 2004-02-09 12:57:46


Victor wrote:

> At Monday 2004-02-09 07:56, you wrote:
> >"Victor A. Wagner, Jr." <vawjr_at_[hidden]> writes:
> >
> > > Of course you cannot portably pass all exceptions, but you may be
> > > able to pass all the ones that use standard types.
> >
> >And what if the std library or somebody else throws exceptions
> >*derived* from the standard types?
>
> I guess I should have said _are_ standard types

Or, at least _are_ in the sense of being equivalent under slicing...

> We can either do nothing (until the standard changes so we
> can handle ALL
> types) or we can do something (handle the built-in types and
> the standard exceptions).
>
> I suggest "something" as a useful approach.

Whimsical idea: could we use type lists, so we could instantiate a thread
starter
template with the list of exceptions it should wrap, and get slicing
semantics
into the calling context? All other exceptions would fall through, but then
the user can enumerate the "most possible" exceptions.

/David


Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk