Changes between Version 51 and Version 52 of Developer/Projects/SequencedInitialization

Timestamp:

06/15/10 16:39:39 (14 years ago)

Author:

Sh

Comment:

Iterate functions

Developer/Projects/SequencedInitialization

@@ -241 +241 @@
    = &SYSINIT_ENTRY_NAME(handler)
 
+ /**
+  * @brief Iterates through all entries of the system initialization set.
+  *
+  * Calls each handler with the @a state parameter.
+  */
+ void _Sysinit_Iterate(Sysinit_State state);
+ 
+ /**
+  * @brief Iterates through all entries of the system initialization set in
+  * reversed order.
+  *
+  * Calls each handler with the @a state parameter.
+  */
+ void _Sysinit_Iterate_reversed(Sysinit_State state);
+
 The implement of referencing the sequenced initialization struct. In the every C source code file include initialization function we define a sequenced initialization struct which contain the init function entry. And then a reference function point will be defined in the another file include a function which will be called if this object is used by application. For example
 ,consider the RTEMS Message API. In the RTEMS Message API's initialization call's source file we create a structure Sysinit_Entry include the field of the RTEMS Message API's initialization call entry. Then we reference this variable from the source file containing the rtems_message_queue_create code. Because the application must make a call to rtems_message_queue_create or all the other Message API calls will fail therefore this API needs only one reference from a single source file. But there is also a exception that if the application use RTEMS Event and RTEMS Signal API there is no similar call like rtems_message_queue_creat which the application must call or it will fail. '''So we must consider another method to solve this problem. Now we donot have a better way to fix it.'''