boost.threads [was RE: [boost] Re: sockets /network programming Requirements]

From: williamkempf_at_[hidden]
Date: 2001-08-03 15:53:18

--- In boost_at_y..., "Alexander Terekhov" <terekhov_at_d...> wrote:
> 
> > In case I've not convinced you yet, here are two other core 
language
> > issues with this approach.
> >
> > 1) If while processing an exception a local is destroyed whose
> > destructor throws an exception, terminate will be called. (15.2/3)
> >
> > 2) Consider the following: void foo() throw() { bar(); }.
> >
> > What's needed is exception style stack unwinding with no 
possiblity
> > of the user circumventing things.
> 
> what ?!
> 
> ever heard of Java's InterruptedException and
> usage patterns like

[snip]

> ????

I said circumvent, not interact with.  The two core language issues 
above makes the Java style exception mechanism simply not work.  C++ 
isn't Java.

> thread return value aside, thread::exit() should be equal
> to this_thread->interrupt() / throw InterruptedException().

I don't agree.  We could debate that for some time, but since the 
concept is broken in C++ any way, I won't bother.

Bill Kempf