Subject: Re: [boost] [threadpool] new version v12
From: Peter Dimov (pdimov_at_[hidden])
Date: 2008-11-03 10:42:47
> No, I'm not sure, but if some_future.wait() switches to a new fiber I
> am concerned that it won't, because the exception state is per-thread,
> not per-fiber.
On second thought, yes, it might be possible to construct an example that
breaks. You need to switch to another fiber in a catch clause, which then
needs to throw _and_ switch back to you in a catch clause. Another
problematic case is switching to another fiber during stack unwinding.
I'm not sure if this can happen in practice in a straightforward pool
implementation that only yields on wait. A waits for B waits for A is a
-- Peter Dimov http://www.pdplayer.com
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk