Re: [Xenomai-help] Application broken 2.3.4 ---> 2.4.0

["Ignacio García Pérez" <iggarpe@domain.hid>]

Jan Kiszka escribió:
> That's due to the reworked timer subsystem: Starting timers (like the
> periodic task timer) in the past is reported as error - up to the
> application in this case. One may discuss if this case can be considered
> as an undocumented API change (I haven't re-read the docs in this regard
> yet).
>   
I correct myself. The API actually states that the -ETIMEDOUT error code 
will be return if passed idate is in the past. But that is true for the 
2.3.x series and for the new 2.4.0 version.

Which means that the true difference between 2.3.x and 2.4.0 is that:

2.3.x: returns -ETIMEDOUT but schedules the task for immediate execution.

2.4.0: returns -ETIMEDOUT and *does not* schedule the task for immediate 
execution.

The more I think about it the mode I think this is a bug.

I just can't think of a situation in which idate is in the past and it 
makes sense *not scheduling* the task for immediate execution...