From: Mathias Gaunard (mathias.gaunard_at_[hidden])
Date: 2008-07-25 08:44:51
atkinson julian wrote:
> Hi, the combination of asio and coroutines would seem to represent a little
> bit of magic (layering a linear code model over an async event framework and
> without the attendant issues involved in multithreading).
Yes, it would be pretty cool.
However, couldn't the syntax be directly that of blocking asio calls?
coro::future<error_type, iterator_type> future(self);
is really the same thing as
tuple<error_type, iterator_type> result = resolver.resolve(query);
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk