On Sat, Dec 13, 2014 at 07:01:12PM -0800, Jerry DeLisle wrote: > of the tasker to the underlying OS so the infinite loops don't burn CPU > cycles uselessly.
Note that in classical Forth multitaskers MS yields (pauses) until the time has passed, and if no other task wants to do something, the multitasker busily visits all the tasks. Gforth was originally not designed for multi-tasking, and had an MS that did not PAUSE; I don't know if that has changed, but eventually, it should. Nowadays one usually wants to save the power and/or leave the CPU to other processes, and this can be achieved with a bit of additional complication in the scheduler. - anton
