onto the server (to send messages) and a boolean indicating whether we are
done or not, just like we did on the server side in \ref
GRAS_tut_tour_globals. Here is the resulting global structure:
-\dontinclude 7-timers.c
+\dontinclude 07-timers.c
\skip client_data
\until client_data_t
periodicity at which it was desinstalled (so that the same action can be
scheduled at different intervals, and each of them be desinstallable
separately).
-\dontinclude 7-timers.c
+\dontinclude 07-timers.c
\skip gras_timer_cancel_repeat
\until gras_timer_cancel_repeat
be self-explanatory at this point. It could be cancelled before its
expiration using gras_timer_cancel_delay(), which accepts exactly the same
kind of arguments than gras_timer_cancel_repeat().
-\dontinclude 7-timers.c
+\dontinclude 07-timers.c
\skip client_do_stop
\until end_of_client_do_stop
\section GRAS_tut_tour_timers_recap Recapping everything together
The program now reads:
-\include 7-timers.c
+\include 07-timers.c
Which produces the expected output:
-\include 7-timers.output
+\include 07-timers.output
Go to \ref GRAS_tut_tour_exceptions
