29 Apr
2013
29 Apr
'13
8:21 p.m.
2013/4/29 Niall Douglas <ndouglas@blackberry.com> The idea is that the engine is fairly generic for anywhere where you
do need to chain lots of coroutine type items together (not that it supports Boost.Coroutine yet). v1 isn't particularly generic nor optimal, but I'm hoping with feedback from Boost that v2 in a few years' time would be much improved.
you should take a look at boost.fiber (github.com/olk/boost-fiber) - it schedules 'tasks' cooperativly (including waiting for other fibers, future etc.). It is based on boost.context (as boost.coroutine does).