|
Boost : |
From: Johan Torp (johan.torp_at_[hidden])
Date: 2008-06-03 06:26:30
Peter Dimov-5 wrote:
>
> A future-based interface built on top of a callback interface doesn't seem
> to suffer from the deficiencies you list, and neither does a message-based
> interface (given an appropriately powerful and robust message-passing
> framework in which to express it.)
>
One of my points is valid even for these two cases. The future-interface
allows the promise-fulfiller to detect that all associated futures has died
and that it needn't fulfill the request. That is, if we add this
functionality to the promise class.
Johan
-- View this message in context: http://www.nabble.com/-future--Early-draft-of-wait-for-multiple-futures-interface-tp17242880p17620427.html Sent from the Boost - Dev mailing list archive at Nabble.com.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk