Clarifications

[2shaar2059]

1. In SCH_DefaultScheduleTable (from sch_def_schtbl.c), is there a particular reason that certain entries are commented out and have their EnableState set to SCH_DISABLED? Isn't this redundant (i.e. does this have the same result as simply uncommenting those lines and keeping their disabled status)?
2. Can the order of entries in SCH_DefaultScheduleTable be rearranged without affecting the results of the scheduler app?
3. Despite being commented out, is there a particular reason for putting entries with different MessageIndex out of order and spaced out by several SCH_UNUSED entries? For example, the following lines of code are seperated by many SCH_UNUSED entries and appear out of order by MessageIndex
   /*{ SCH_DISABLED, SCH_ACTIVITY_SEND_MSG, 4, 1, 6, SCH_GROUP_CFS_HK }, */ /* CS HK Request */ has a MessageIndex of 6 and appears on line 122
   /*{ SCH_DISABLED, SCH_ACTIVITY_SEND_MSG, 1, 0, 24, SCH_GROUP_MD_WAKEUP }, */ /* MD Wakeup */ has a MessageIndex of 24 and appears on line 130
   /*{ SCH_DISABLED, SCH_ACTIVITY_SEND_MSG, 4, 2, 7, SCH_GROUP_CFS_HK }, */ /* DS HK Request */ has a MessageIndex of 7 and appears on line 159

4./*{ SCH_DISABLED, SCH_ACTIVITY_SEND_MSG, 1, 0, 24, SCH_GROUP_MD_WAKEUP }, */ /* MD Wakeup */ appears 20 times in the file. Is there a reason for this?
5. Is there any significance to separating entries into slots of 5 (or slots at all) in the layout of the array? Is this simply a matter of styling or is there a concept of slots in the code too? If so, what is the point of that?