> Le 25 oct. 2017 à 17:55, Douglas von Roeder via 4D_Tech > <[email protected]> a écrit : > > Arnaud: > > My understanding is that, given that 4D's scheduler has been "cooperative > multitasking" for virtually all of its history, the Idle command instructs > the current process to yield time to other processes. Without the While…End > while loop and the Idle command, the current process would hit the > Semaphore command and processing would stop until 300 ticks had passed. > That process would not yield CPU, causing all processing to stop.
Yes, but when I look at examples in the Semaphore function, only the 1 (the oldest?) uses while+idle. And I remember Olivier Deschanels saying during a training that the second parameter was made to limit the delay. Now, is it "a" way to delay, "the" way, when to mix both? That's what I'd like to know. And more specifically with a global semaphore, as in David's situation. -- Arnaud de Montard ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
