On Wed, Apr 11, 2012 at 10:41 PM, Oliver Kowalke <oliver.kowalke@gmx.de>wrote:
Hi,
unfortunetly Giovanni decided to discontinue its boost.coroutine library and I was ask be several members of the boost community to provide a coroutine implementation using boost.context. I've refactored class context from lib boost.context so that I can provide coroutine<> and generator<> (following Giovannis interface proposal) based on context now. I'd like to split it into two libraries:
- boost.context provides only context jumping facility (a.g. struct fcontext_t, start_fcontext()/jump_fcontext()/make_fcontext() and stack helper)
- boost.coroutine contains coroutine<> and generator<>
Might this be appropriate?
My preference at this phase in the moon (i.e., just thinking aloud at the moment) might be to have everything context-related be under a single heading, rather than be fragmented, just to express their close relationships. It might be easier then for someone who first looks at context to immediately realize that what they really want is one of the higher-level constructs. I might be worried about a non-existent problem, though! Suggestions for such a single heading, if we go that route: Fiber? Cooperative? My 2c, - Jeff