That's only one particular use case. Clearly we're talking about two different viewpoints where mine focusses on a very broad application for this kind of library, while yours is trying to limit it to a small set of use cases. While I accept the validity of these use cases I think it's not worth having a full Boost library just for those.
Hmm! With respect, it sounds to me as though you're saying: my use case is important, yours is not.
Please don't start splitting hairs. I said 'While I accept the validity of these use cases' after all.
You're saying that for your use case, performance is critical, and performance would be the only reason you would choose Boost.Fiber over other libraries available to you. I can respect that.
I'm saying that for my use case, performance is not critical, and there is nothing in the standard library or presently in Boost that addresses my semantic requirements. That sounds like reason enough to have a Boost library.
Fine. So you vote YES and I vote NO. What's the problem? Regards Hartmut --------------- http://boost-spirit.com http://stellar.cct.lsu.edu