6 Jan
2012
6 Jan
'12
1:34 p.m.
I'm sorry I omitted your first mail suggestion of Boost.Context. Context is a really good way for yielding. It will be a stargate to another world. Safety is the most important, and It's can be designed for a normal function, not only for the Phoenix. 2012/1/6 Mathias Gaunard <mathias.gaunard@ens-lyon.org>:
On 01/06/2012 11:25 AM, Huang Huan wrote:
None of local vars will be destructed after once yielding, Hold the stack object for next yielding call. How can I get this without virtual stack?
Use special instructions or OS-provided functions to save the context and switch to another context.
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost