#include int main() { while(!DONE) { /* check for stuff */ } return 0; }
The above code sample uses 100% cpu until DONE
If I'm guessing correctly (I don't know about it), the equivalent of App.ProcessMessages is doing blocking IO. And as I don't know of any implementation of C on multitasking OS which uses polling, any standard C IO should be safe.