Opinions?
Two options with distinguishable syntax.
var1: int;
threasafe var1: int;
or
var1: int threadsafe;
--
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs y
On Sunday 11 May 2014 10:30:13 Ivanko B wrote:
> Opinions?
>
> Two options with distinguishable syntax.
>
> var1: int;
>
> threasafe var1: int;
> or
> var1: int threadsafe;
>
Have you ever concurrentely read strings from different threads?
Martin
-
On Saturday 10 May 2014 18:03:05 Med Hamza wrote:
> Hi Martin,
>
>I think there is an other bug when we want to maximize and restore
> window.
> Linux Puppy ver 5.7 system distro.
>
https://github.com/joewing/jwm/issues/115
https://github.com/joewing/jwm/issues/116
https://github.com/joewing/j
It's OK with IceWM Manager.
Thank you.
2014-05-11 13:54 GMT+01:00 Martin Schreiber :
> On Saturday 10 May 2014 18:03:05 Med Hamza wrote:
> > Hi Martin,
> >
> >I think there is an other bug when we want to maximize and restore
> > window.
> > Linux Puppy ver 5.7 system distro.
> >
> htt
Have you ever concurrentely read strings from different threads?
==
With memory access hooks etc ? No, but there may be such need - it's
even obvious from Your question.
--
Is your legacy SCM system hol
I looks like DB issues about concurrent accessing shared data.
There're a few 100% working access disciplines for that - SHARE, SHARE
READ, SHARE EXCLUSIVE etc. For instance, they may introduce read
waiting for another's change to commit. How about implemention those
with thread-safe variables ?
-
6 matches
Mail list logo
