nobody wrote on Saturday, November 27, 2004:
I’m quite interested in the FreeRTOS project (and thank you for your effort!).
However, I was wondering why the timer tick is not a (signed) long so that a -1 can be used for a forever wait (blocking read)?
At the moment if I want to block forever I cannot. I must pass it ULONG_MAX but expect to wake up in about 42 days with a 1KHz tick (or 420 days with 10ms tick).
At any rate, anyone that can live with blocking for many days (if that’s what they want) can also live with “many days”/2 (by using signed).
But for folks where “many days” == forver, I now don’t have to put code everywhere to check of my call came back due to a timeout and now I have to call it again!
ALSO (2nd Q):
Is the timer tick over flow handled properly in the kernel? Since even a 10ms tick will result in 400+ days before overflow, if not checked explicitely a problem with it may have gone un-noticed.
ALSO (3rd Q :):
Why no timer functionality in FreeRTOS?