Subject: Re: [boost] Mixing async/sync code thanks to boost::context
From: Christophe Bailly (chbailly_at_[hidden])
Date: 2018-12-15 00:18:52
I made many efforts to make this clear, this was sent also to the
I won't insist in this mailing list if nobody is interested in the idea
Here is my mail:
I have worked on a prototype to avoid the current limitations with async
code, the use of sync + async code is really difficult, it does not
co-exist easily. If you introduce async code, you have to migrate all your
code ... There are alternative solutions (threads..) but here is a
suggestion to overcome these limitations.
It is currently a very simple prototype but I would be interested to have
your feedback. I think this kind of solution can be really powerfull, but I
will wait to know what you think about it.
Here are the links:
On Wed, 12 Dec 2018 at 02:11, Gavin Lambert via Boost <boost_at_[hidden]>
> On 12/12/2018 13:31, Christophe Bailly wrote:
> > It is not really a question about using library but a question/suggestion
> > about another possible implementation of async code.
> Which is still a usage of a library.
> > The code posted works, is asynchronous though there is a synchronous call
> > in the middle (by synchronous I mean the function is written just like a
> > synchronous function, nothing to change).
> Coroutines look like synchronous code, but they are still asynchronous
> because they can be suspended and resumed at yield points. It is still
> problematic to block without yielding.
> Have a look at the examples provided with Boost.Asio.
> Unsubscribe & other changes:
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk