This function is invoked at the immediate beginning of application initialization. It is the very first function to be executed at system startup. User supplied implementation of this function should be restricted to things like memory initialization, early hardware duties, etc.

        void UserInitializationCalloutf()
        {
          /* Insert implementation specific code here.  */
        }
        

This function is invoked immediately prior to executing any xtUML application initialization function.

        void UserPreOoaInitializationCalloutf()
        {
          /* Insert implementation specific code here.  */
        }
        

This function is invoked immediately after executing any/all xtUML application initialization function(s). When this callout function returns, the system dispatcher will allow the xtUML state models to start consuming events.

        void UserPostOoaInitializationCalloutf()
        {
          /* Insert implementation specific code here.  */
        }
        

This function is invoked once during each loop execution of the system dispatcher. (This may be an excellent place to hang an invocation to a timer (TIM) tick routine.)

        void UserBackgroundProcessingCalloutf()
        {
          /* Insert implementation specific code here.  */
        }
        

This function is invoked at termination of the system dispatcher, but prior to performing any xtUML application shutdown sequencing.

        void UserPreShutdownCalloutf()
        {
          /* Insert implementation specific code here.  */
        }
        

This function is invoked immediately before application exit.

        void UserPostShutdownCalloutf()
        {
          /* Insert implementation specific code here.  */
        }
        

This function is invoked any time that an event is received that results in a ``can't happen'' transition.

Where the input parameters are:

        void UserEventCantHappenCallout( const Escher_StateNumber_t current_state,
                                         const Escher_StateNumber_t next_state,
                                         const Escher_EventNumber_t event_number
        )
        {
          /* Insert implementation specific code here.  */
        }
        

This function is invoked any time that an event is received and there is no target instance to receive it. This often means that the instance was deleted while the event was in flight. Usually this indicates a modeling error. The default behavior without supplying a body to this function is simply to consume the event and go on.

Where the input parameters are:

        void UserEventNoInstanceCallout( const Escher_EventNumber_t event_number
        )
        {
          /* Insert implementation specific code here.  */
        }
        

This function is invoked when an attempt is made to allocate an event, but there are no more left.

        void UserEventFreeListEmptyCalloutf()
        {
          /* Insert implementation specific code here.  */
        }
        

When marked active, this function is invoked when an attempt is made to use an instance reference variable (handle) that is null (empty).

        void UserEmptyHandleDetectedCallout( const char * object_keyletters,
                                             const char * s )
        {
          /* Insert implementation specific code here.  */
        }
        

This function is called from instance creation methods when an attempt is made to create an instance of an object and no allocation units are available.

        void UserObjectPoolEmptyCallout( const char * domain,
                                         const char * object_name )
        {
          /* Insert implementation specific code here.  */
        }
        

MC-3020 uses a collection of set ``containoids'' to link data items together in lists. These utility list nodes are used collecting extents, events and relationships. In the situation that an attempt is made to allocate a node, but none are available, this function will be called.

        void UserNodeListEmptyCalloutf()
        {
          /* Insert implementation specific code here.  */
        }
        

MC-3020 uses an array as a queue to manage invocations of interleaved bridges (bridge operations marked safe for interrupt invocation). UserInterleavedBridgeOverflowCallout is invoked when an attempt is made to post too many interleaved bridges. The depth of this list is defined by SYS_MAX_INTERLEAVED_BRIDGES (unless changed in the rule file).

        void UserInterleavedBridgeOverflowCalloutf()
        {
          /* Insert implementation specific code here.  */
        }
        

If the user wishes to gain control of processing when either of the two event queues are empty (no events to be processed at the current time), two callouts are provided. UserSelfEventQueueEmptyCallout and UserNonSelfEventQueueEmptyCallout are invoked (assuming they are enabled) each time the corresponding event queue is interrogated and found to be empty.

        void UserSelfEventQueueEmptyCalloutf()
        {
          /* Insert implementation specific code here.  */
        }
        void UserNonSelfEventQueueEmptyCalloutf()
        {
          /* Insert implementation specific code here.  */
        }