Re: use (storage)

2019-02-01 Thread Keisuke Miyako via 4D_Tech
"Use" locks shared objects by locker ID. if you write Use (Storage) Storage.prop:=New shared object End use trace it, and enabled "display type" in the debugger pane, you would see that the locker id of Storage is -7 (don't ask me why). Storage.prop would be -15 (ditto)

Re: use (storage)

2019-02-01 Thread Jeremy French via 4D_Tech
Hi David, No locking occurs with "Use (Storage)” by itself. But locking does occur for **first level** attributes of Storage. So “Use (Storage.pref)” performs locking in other processes. To prevent “Storage.pref” from being updated in a separate process, call: Use (Storage.pref) //

Re: use (storage)

2019-02-01 Thread Christian Sakowski via 4D_Tech
> My test show that > > Use(Storage) > …. > > Does not lock Storage.pref, and does not prevent Storage.pref from being > updated in a separate process. > > By lock, I mean that during use(Storage) in process A, use(Storage.pref) in > process B will execute without waiting.

use (storage)

2019-02-01 Thread David Ringsmuth via 4D_Tech
My test show that Use(Storage) …. Does not lock Storage.pref, and does not prevent Storage.pref from being updated in a separate process. By lock, I mean that during use(Storage) in process A, use(Storage.pref) in process B will execute without waiting. By update I mean