From: Victor A. Wagner, Jr. (vawjr_at_[hidden])
Date: 2002-08-13 15:20:33
At Tuesday 2002/08/13 12:03, you wrote:
>----- Original Message -----
>From: "Eric Woodruff" <Eric.Woodruff_at_[hidden]>
> > So, it seems exception hierarchies are not feasible unless the abstract
> > provides a clone () method. We could possibly implement cloning wrappers
> > std::exceptions and then unwrap them at the other end.
> > For user exception hierarchies, they would have to follow the same clone
> > semantics.
> > How often does a user need to support entire exception hierarchies across
> > threads?
>Is it ever useful to know what the exception type is in this case? I ask,
>because it seems to me that there's no way to recover in this case, and the
>only reason for propogation is to give some possibility for a clean exit
>instead of an abrubt halt. If you can't recover, then what need is there
>for knowing the exception type?
Some of us plan on using boost::thread to implement separation of call and
>Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Victor A. Wagner Jr. http://rudbek.com
PGP RSA fingerprint = 4D20 EBF6 0101 B069 3817 8DBF C846 E47A
PGP D-H fingerprint = 98BC 65E3 1A19 43EC 3908 65B9 F755 E6F4 63BB 9D93
The five most dangerous words in the English language:
"There oughta be a law"
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk