Re: [certi-dev] Time advancement

[Eric Noulard]

2010/11/19 Eric Noulard <address@hidden>:
> 2010/11/19 Michael Raab <address@hidden>:
>> Hi Eric, hi all
>>
>> may someone can give me a short description of the different TICK_STATE
>> types, to give me a better understanding of there meaning:
>
> I'll try sum-up a useful description later by the end of the morning.
> I'll certainly put comment directly in the source code.

    enum {
        NO_TICK,        /*!< No tick request received from federate */
        TICK_BLOCKING,  /*!< A 'blocking' tick request has been received */
        TICK_NEXT,      /*!< This is the continuation state of a previous
                             (blocking with timeout) tick request */
        TICK_CALLBACK,  /*!< Time management needs to treat a Callback */
        TICK_RETURN     /*!< Time management will terminate the tick call
                             because of an error in a callback or
because this is the end
                             (timeout)
                         */
    } _tick_state;

Hi sorry but I have been pre-empted by other activies.
I did commit the previous comment inside TimeManagement.hh.

I's clearly not enough i'm preparing a cleaner automaton description
with Uppaal.
this will be in there: certi/doc/CERTI-tickHandling.xml
this is not uisable yet (Work in progress)
I'll tell you when I'm done.
-- 
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.org