[En-Nut-Discussion] NutEventWait - Suggested Change

[Radek Podgorny]

Yeah, I second that. Last time it took me way too much time to figure out 
what's going on. I expected the value of zero to make it work in a 
non-blocking way... :-(

Radek P.

> 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.
> _______________________________________________
> En-Nut-Discussion mailing list
> En-Nut-Discussion at egnite.de
> http://www.egnite.de/mailman/listinfo.cgi/en-nut-discussion

-- 
GnuPG key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x98E56D84
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.egnite.de/pipermail/en-nut-discussion/attachments/20050113/e218acbc/attachment-0001.pgp>