[boost] Re: future of boost.threads

From: David Abrahams (dave_at_[hidden])
Date: 2004-02-10 12:08:47

"Victor A. Wagner, Jr." <vawjr_at_[hidden]> writes:

> At Monday 2004-02-09 14:18, you wrote:
>>"Brock Peabody" <brock.peabody_at_[hidden]> writes:
>>
>> >> -----Original Message-----
>> >> From: boost-bounces_at_[hidden] [mailto:boost-bounces_at_[hidden]]
>> >> On Behalf Of Victor A. Wagner, Jr.
>> >
>> >> 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.
>> >
>> > I'd suggest allowing the user to specify a typelist rather than hard coding
>> > the standard types.  You could supply as a default the list of standard
>> > types.
>>
>>There are better ways.  Boost.Python uses a dynamic registration
>>technique.  Compile-time enumeration of the exceptions is overkill
>>and not sufficiently flexible.
>
> I'm all ears to hear about runtime exception detection and classification
> what syntax for the compiletime catch() do you expect to use?

Use the source, Luke.  It's all there in your CVS snapshot.  Doesn't
handle ordering of base and derived classes, though.

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com