From: David Abrahams (dave_at_[hidden])
Date: 2004-02-12 08:10:07
Sam Partington <Sam.Partington_at_[hidden]> writes:
> On Wed, 11 Feb 2004 13:26:27 -0600, Brock Peabody
> <brock.peabody_at_[hidden]> wrote:
>> Just to prove to myself that I could do it I implemented a rough
>> version of
>> what I was talking about. I think the interface is pretty easy to use.
>> exception_transporter.h - non thread related tool for transporting
>> exceptions in a typelist. Could be used for other areas where
>> exceptions propagation is an issue. Returns exceptions in a
>> variant so the user can inspect or throw them.
>> thread_with_exceptions.h - used like:
>> thread_with_exceptions<exception_type_list, return_type>
>> //may propagate an exception from the list
>> return_type rval = t.join();
>> main.cpp - implements a small example.
>> Does this seem like a reasonable approximation of what people have been
>> asking for?
> All looks fine to me, but without meaning to sound rude, what does it
> give you over the implementation I posted two days ago?
And what about the one Daniel Wallin posted, which doesn't require
all exceptions to be registered in one big compile-time list?
-- Dave Abrahams Boost Consulting www.boost-consulting.com
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk