asio 0.3.8rc3 | Home | Reference | Tutorial | Examples | Design

Tutorial

# Timer.3 - Binding arguments to a handler

In this tutorial we will modify the program from tutorial Timer.2 so that the timer fires once a second. This will show how to pass additional parameters to your handler function.

    #include <iostream>
    #include <asio.hpp>
    #include <boost/bind.hpp>
    #include <boost/date_time/posix_time/posix_time.hpp>

To implement a repeating timer using asio you need to change the timer's expiry time in your callback function, and to then start a new asynchronous wait. Obviously this means that the callback function will need to be able to access the timer object. To this end we add two new parameters to the `print` function:

- A pointer to a timer object.

- A counter so that we can stop the program when the timer fires for the sixth time.

    void print(const asio::error_code& /*e*/,
        asio::deadline_timer* t, int* count)
    {

As mentioned above, this tutorial program uses a counter to stop running when the timer fires for the sixth time. However you will observe that there is no explicit call to ask the io_service to stop. Recall that in tutorial Timer.2 we learnt that the asio::io_service::run() function completes when there is no more "work" to do. By not starting a new asynchronous wait on the timer when `count` reaches 5, the io_service will run out of work and stop running.

      if (*count < 5)
      {
        std::cout << *count << "\n";
        ++(*count);

Next we move the expiry time for the timer along by one second from the previous expiry time. By calculating the new expiry time relative to the old, we can ensure that the timer does not drift away from the whole-second mark due to any delays in processing the handler.

        t->expires_at(t->expires_at() + boost::posix_time::seconds(1));

Then we start a new asynchronous wait on the timer. As you can see, the boost::bind function is used to associate the extra parameters with your callback handler. The asio::deadline_timer::async_wait() function expects a handler function (or function object) with the signature `void(const asio::error_code&)`. Binding the additional parameters converts your `print` function into a function object that matches the signature correctly.

See the Boost.Bind documentation for more information on how to use boost::bind.

In this example, the asio::placeholders::error argument to boost::bind is a named placeholder for the error object passed to the handler. When initiating the asynchronous operation, and if using boost::bind, you must specify only the arguments that match the handler's parameter list. In tutorial Timer.4 you will see that this placeholder may be elided if the parameter is not needed by the callback handler.

        t->async_wait(boost::bind(print,
              asio::placeholders::error, t, count));
      }
    }

    int main()
    {
      asio::io_service io;

A new `count` variable is added so that we can stop the program when the timer fires for the sixth time.

      int count = 0;
      asio::deadline_timer t(io, boost::posix_time::seconds(1));

As in Step 4, when making the call to asio::deadline_timer::async_wait() from `main` we bind the additional parameters needed for the `print` function.

      t.async_wait(boost::bind(print,
            asio::placeholders::error, &t, &count));

      io.run();

Finally, just to prove that the `count` variable was being used in the `print` handler function, we will print out its new value.

      std::cout << "Final count is " << count << "\n";

      return 0;
    }

See the full source listing
Return to the tutorial index
Previous: Timer.2 - Using a timer asynchronously
Next: Timer.4 - Using a member function as a handler

asio 0.3.8rc3 | Home | Reference | Tutorial | Examples | Design