#define TIME_50HZ 2

while (!lquit)
{
nclock = clock()+TIME_50HZ;

/*do some stuff*/

while (clock() < nclock)
{
}
}

I'm assuming the tight loop is maxing out the CPU until (clock() >= nclock) and as such is probably not a good way to do it. I'm using Norcroft 'C' and was wondering if there is a better way to do this? Is there a sleep() function or similar that is less taxing on the CPU?

Thanks,

Mike.

Failing that, I think that in a single tasking environment just waiting in a tight loop is the only way to go. Any IRQ events etc. can still run their course during that tight loop, so you're not really keeping the CPU from being used for other things.