structure memory optimizations.

[silc.git] / lib / silcutil / silcschedule.h

diff --git a/lib/silcutil/silcschedule.h b/lib/silcutil/silcschedule.h
index 4e079cad980ab504e9eafde6ddf90d54b490c569..f10bd8306ad34e373993902c470732f122164ace 100644 (file)
--- a/lib/silcutil/silcschedule.h
+++ b/lib/silcutil/silcschedule.h
@@ -119,7 +119,7 @@ typedef struct SilcTaskStruct *SilcTask;
 typedef enum {
   /* File descriptor task that performs some event over file descriptors.
      These tasks are for example network connections. */
-  SILC_TASK_FD,
+  SILC_TASK_FD           = 0,
 
   /* Timeout tasks are tasks that are executed after the specified 
      time has elapsed. After the task is executed the task is removed
@@ -190,7 +190,7 @@ typedef enum {
      has expired only and only when every other task with higher priority 
      has already been run. For non-timeout tasks this priority behaves
      same way. Life is not fair for tasks with this priority. */
-  SILC_TASK_PRI_LOW,
+  SILC_TASK_PRI_LOW      = 0,
 
   /* Normal priority that is used mostly in SILC. This is priority that
      should always be used unless you specificly need some other priority.
@@ -590,12 +590,12 @@ void silc_schedule_unset_listen_fd(SilcSchedule schedule, SilcUInt32 fd);
  *    signal system will not work without calling silc_schedule_signal_call
  *    function.  The specified `signal' value will be also delivered to
  *    the `callback' as the fd-argument.  The event type in the callback
- *    will be SILC_TASK_INTERRUPT.  It is safe to use any SILC routines,
+ *    will be SILC_TASK_INTERRUPT.  It is safe to use any SILC routines
  *    in the `callback' since it is actually called after the signal really
  *    happened.
  *
  *    On platform that does not support signals calling this function has 
- *    not effect.
+ *    no effect.
  *
  * EXAMPLE
  *
@@ -653,7 +653,7 @@ void silc_schedule_signal_unregister(SilcSchedule schedule, SilcUInt32 signal,
  *    Mark the `signal' to be called later.  Every signal that has been
  *    registered by silc_schedule_signal_register is delivered by calling
  *    this function.  When signal really occurs, the application is 
- *    responsible of calling this function int the signal handler.  After
+ *    responsible of calling this function in the signal handler.  After
  *    signal is over the scheduler will then safely deliver the callback
  *    that was given to silc_schedule_signal_register function.
  *