[En-Nut-Discussion] NutEventWait - Suggested Change

[Harald Kipp]

Ralph,

This will indeed break almost all existing code.
Anyway, we may consider it for the upcoming 4.0
to get rid of this inconsistency. But I'd like
to hear more opinions first.

Harald


At 09:00 14.01.2005 +1300, you wrote:
>This is probably contentious since it would break lots of existing code.
>
>At the moment Calling NutEventWait with a timeout of 0 makes it wait 
>forever.  I think this is wrong, calling it with a timeout of zero should 
>return the signaled state of the event or return immediately with -1 
>(perhaps with a Yield)
>
>A define of  INFINITE should be make with a value of -1 to do the Job that 
>0 does at the moment.
>
>This means you could do non blocking reads on sockets and devices etc and 
>make it cleaner (IMHO).
>
>
>Ralph.