concurrency

Sean Kelly sean at f4.ca
Mon Feb 4 09:12:12 PST 2008


Jason House wrote:
> Sean Kelly Wrote:
> 
>> Bedros Hanounik wrote:
>>> I think the best way to tackle concurrency is to have two types of functions
>>>
>>> blocking functions (like in the old sequential code execution)
>>>
>>> and non-blocking functions (the new parallel code execution)
>>>
>>> for non-blocking functions, the function returns additional type which is true when function execution is completed
>> This is basically how futures work.  It's a pretty useful approach.
> 
> 
> I've never heard of that.  Does anyone have a good link for extra detail on futures?

Futures are basically Herb Sutter's rehashing of Hoare's CSP model.
Here's a presentation of his where he talks about it:

http://irbseminars.intel-research.net/HerbSutter.pdf


Sean



More information about the Digitalmars-d mailing list