concurrency

[interessted]

hi,

wouldn't it be okay to do it like in 'Active Oberon' (http://bluebottle.ethz.ch/languagereport/ActiveReport.html) or 'Zennon' (http://www.oberon.ethz.ch/oberon.net/)?



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.
> 
> 
> Sean