> Le 25 oct. 2017 à 18:23, Douglas von Roeder via 4D_Tech
> <4d_tech@lists.4d.com> a écrit :
>
> Arnaud:
>
> [...] That is a function of "cooperative multitasking" and, now that we can
> run code
> pre-emotively, developers will have to have a more clear understanding of
> (and better control
Arnaud:
I would say it is "a" way to use a Semaphore and the idea that it is a
limit is the way that I've always understood it.
The fact that it's a gobal semaphore means that it controls access to the
code that follows and the scope of that is for all machines connected to
the server. The
> Le 25 oct. 2017 à 17:55, Douglas von Roeder via 4D_Tech
> <4d_tech@lists.4d.com> 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
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
> Le 25 oct. 2017 à 04:27, David Ringsmuth via 4D_Tech <4d_tech@lists.4d.com> a
> écrit :
>
> The “Semaphore” function is crashing 4D Remote’s connection to 4D Server.
>
> While(Semaphore("MySemaphore";300)) // ←- this line crashes
> // more coding here
> End while
The doc "about semaphore"
The “Semaphore” function is crashing 4D Remote’s connection to 4D Server.
While(Semaphore("MySemaphore";300)) // ←- this line crashes
// more coding here
End while
4D Remote v15.4 Built 32bit on OSX 10.9.5
4D Server v15.4 Built 32bit on OSX 10.9.5 8GB Ram Core 2 Duo
The Client-Server
6 matches
Mail list logo
