Re: [boost] [context/coroutine] split into two libs in trunk?!

Subject: Re: [boost] [context/coroutine] split into two libs in trunk?!
From: Oliver Kowalke (oliver.kowalke_at_[hidden])
Date: 2012-04-12 02:54:46

> 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!
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).
I don't think it is a good idea to put all those stuff into one lib.

regards,
Oliver
-- 
Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir
belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de