Re: [boost] Attempting resolution of Threads & Exceptions Issue

From: Victor A. Wagner, Jr. (vawjr_at_[hidden])
Date: 2002-08-13 16:29:27

At Tuesday 2002/08/13 13:01, you wrote:
>From: "Victor A. Wagner, Jr." <vawjr_at_[hidden]>
> > >
> > >Even that's not enough; you need to know the order in which to look for
> > >them:
> > >
> > >try { something(); }
> > >catch(std::exception) {
> > >     std::cout << "x";
> > >}
> > >catch(std::bad_alloc) {
> > >     std::cout << "y";
> > >}
> > >
> > >Never prints "y".
> >
> > of course. the texts I read on exceptions made this quite clear. I don't
> > see this as any sort of a "problem".
>
>Yes, but the user won't be writing that in this case. It's important to
>recognize the limitations of any such system. What does the user actually
>need to get right in order to make it work? He must supply a complete list
>of every concrete exception type that may escape the thread sorted in
>reverse topographical order.

I believe I proposed automagically handling the collection of 
std::exception as one of the policies.  I remember offering to assist in 
writing such a thing.

>-Dave
>
>-----------------------------------------------------------
>            David Abrahams * Boost Consulting
>dave_at_[hidden] * http://www.boost-consulting.com

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"