Boost Users :
Subject: Re: [Boost-users] [Boost.Asio] defer, dispatch and post differences?
From: Richard Hodges (hodges.r_at_[hidden])
Date: 2018-01-05 09:10:33
*post* used to cause the handler to be executed some time in the future on
a thread associated with the executor. It was guaranteed not to happen
*dispatch* used to:
a. if called by a thread currently associated with the executor, cause
the handler to happen now.
b. otherwise behave as per post.
Has this really changed, or does the documentation have an error?
On 5 January 2018 at 08:45, Vinnie Falco via Boost-users <
> On Thu, Jan 4, 2018 at 8:46 PM, Daniel BergstrÃ¶m via Boost-users
> <boost-users_at_[hidden]> wrote:
> > The free functions defer, dispatch and post all have the exact same set
> > overloads and description in the library's reference (version 1.66.0).
> My understanding is that the post and defer functions replace the old
> asio_handler_is_continuation mechanism. See:
> Boost-users mailing list
Boost-users list run by williamkempf at hotmail.com, kalb at libertysoft.com, bjorn.karlsson at readsoft.com, gregod at cs.rpi.edu, wekempf at cox.net