|
Boost : |
Subject: Re: [boost] [thread] Dividing into Boost.Thread and Boost.Sync
From: Oliver Kowalke (oliver.kowalke_at_[hidden])
Date: 2013-08-17 14:48:49
2013/8/17 Andrey Semashev <andrey.semashev_at_[hidden]>
> You can use future and promise to pass asynchronous values, true. But
> still,
> its primary use is with threads. Things like async() and future.then() use
> threads to carry out actions. Even if you don't use these features, you can
> still use futures from Boost.Thread.
>
I mean using fibers instead threads
> Note that I'm not saying there's no point in loosening this dependency of
> futures on threads. I'm saying that Boost.Sync doesn't look like a proper
> place for futures.
>
maybe boost.future?
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk