Boost logo

Boost :

From: Eric Woodruff (Eric.Woodruff_at_[hidden])
Date: 2002-08-13 13:38:26

So, it seems exception hierarchies are not feasible unless the abstract type
provides a clone () method. We could possibly implement cloning wrappers for
std::exceptions and then unwrap them at the other end.

For user exception hierarchies, they would have to follow the same clone ()

How often does a user need to support entire exception hierarchies across

----- Original Message -----
From: David Bergman
Newsgroups: gmane.comp.lib.boost.devel
Sent: Tuesday, 2002:August:13 2:06 PM
Subject: RE: Re: Re: Re: Re:Re:AttemptingresolutionofThreads&ExceptionsIssue


Have you heard about luck? With a lot of luck, that exception object
might be intact, so let's rethrow it as quickly as we can ;-)


-----Original Message-----
From: boost-bounces_at_[hidden]
[mailto:boost-bounces_at_[hidden]] On Behalf Of David Abrahams
Sent: Tuesday, August 13, 2002 1:34 PM
To: boost_at_[hidden]
Subject: Re: [boost] Re: Re: Re: Re:

----- Original Message -----
From: "Eric Woodruff" <Eric.Woodruff_at_[hidden]>
To: <boost_at_[hidden]>
Sent: Tuesday, August 13, 2002 1:49 PM
Subject: [boost] Re: Re: Re: Re: Re:

> You would either:
> 1) specify std::exception& because you want to use the abstract
> 2) specify your error class
> where it would store either:
> 1) an std::exception& which would have a reference to your error type
> 2) an instance of your error class (copy constructed)

2) is viable; 1) is not. The referenced exception object is destroyed
the catch block exits.

           David Abrahams * Boost Consulting
dave_at_[hidden] *

Unsubscribe & other changes:

Unsubscribe & other changes:

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