From: Hartmut Kaiser (hartmut.kaiser_at_[hidden])
Date: 2007-03-09 14:57:52
Braddock Gaskill wrote:
> I just started looking at the boost::futures zip file in the
> vault as well. I'd really like to use it for a current
> project if it is near maturity.
It's far from mature. Just a first (but functional) sketch.
> Can I use it in conjunction with my own thread pool or with
> an active object?
If you write the thread pool or active object support, certainly. The
library as is doesn't know anything about thread pools or active objects. It
just spawns a new thread for every future.
> For example, I'd want something like:
> int f();
> future<int> val = myThreadPool.queue<int>(f);
val.cancel() isn't supported at all, mainly because Boost.Thread doesn't
> The documentation is incomplete except for the simple case,
> which appears to spawn a new thread for every new future?
> The ability to use a future with the asio::io_service in
> particular would be quite powerful.
Agreed. And I'm happy to assist, if needed.
> Braddock Gaskill
> Dockside Vision Inc
> On Tue, 20 Feb 2007 12:11:56 -0800, Sohail Somani wrote:
> > I was looking at the futures implementation in the boost vault. It
> > looks very promising, I must say. One of the open issues however is
> > thread cancellation which I imagine will be important in
> the case of the "or"
> > futures group.
> > Has there been any progress on this front? One of the
> coolest things
> > about boost libraries has been the gradual improvement of
> legacy C/C++
> > code by non-invasive means. I can't imagine solving this problem
> > without invasive means (or traditionally undesirable means, i.e.
> > something like
> > thread->die()). I'm not saying that its non-invasive or nothing, but
> > there are people smarter than me working on this problem!
> > Thanks in advance,
> > Sohail
> > _______________________________________________
> > Unsubscribe & other changes:
> > http://lists.boost.org/mailman/listinfo.cgi/boost
> Unsubscribe & other changes:
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk