On Wed, Apr 11, 2012 at 11:54 PM, Oliver Kowalke <oliver.kowalke@gmx.de>wrote:
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?
not fiber!
I take this to mean you don't like the name "fiber".
the reason I'm asking is that beside of boost.context (which should work as the basis for libs dealing with cooperative tasking) I've now a coroutine library (as requested by some memebers) and I've also the boost.stratified library almost ready (see stratified JS - cooperative too).
What do you mean by "see stratified JS - cooperative too"?
I don't think it is a good idea to put all those stuff into one lib.
I sympathize. I'm just looking to prevent over-fragmentation...Boost already has a lot of libraries, I mean, I'd imagine the number is large enough to be quite unwieldy to those new to Boost :/ And, to reiterate, I don't think it's totally crazy to put all the cooperative stuff under one heading. But maybe I'm just playing devil's advocate. Others should chime in. - Jeff