Linked by Hadrien Grasland on Fri 27th May 2011 11:34 UTC
General Development After having an interesting discussion with Brendan on the topic of deadlocks in threaded and asynchronous event handling systems (see the comments on this blog post), I just had something to ask to the developers on OSnews: could you live without blocking API calls? Could you work with APIs where lengthy tasks like writing to a file, sending a signal, doing network I/O, etc is done in a nonblocking fashion, with only callbacks as a mechanism to return results and notify your software when an operation is done?
Thread beginning with comment 474868
To read all comments associated with this story, please click here.
by braddock on Sat 28th May 2011 00:49 UTC
Member since:

This type of asynchronisity becomes easy to handle with the concept of the "future" primitive.

Reply Score: 2

RE: futures
by Alfman on Sat 28th May 2011 02:36 in reply to "futures"
Alfman Member since:


"This type of asynchronisity becomes easy to handle with the concept of the 'future' primitive."

That is very interesting, it'd be worth having it's own article.

We leave variables undefined in algebra all the time, however the concept of not-yet-defined variables in a language like C++ is intriguing...

I have to ask, is this functionality different from lazy evaluation in lisp-like languages?

Edited 2011-05-28 02:39 UTC

Reply Parent Score: 2