On 05/11/2014 10:50 AM, Martin Schreiber wrote:
Have you ever concurrentely read strings from different threads?
I do this all the time.
-Michael
--
Accelerate Dev Cycles with Automated Cross-Browser Testing - For
On 05/11/2014 08:06 AM, Martin Schreiber wrote:
Hi,
Because of the big overhead by locked refcount operations and memory barriers
long strings and dynamic arrays are not thread safe, even reading needs
serializing if the data will be accessed from several threads.
In exactly what environment
On Monday 12 May 2014 09:37:25 Michael Schnell wrote:
On 05/11/2014 08:06 AM, Martin Schreiber wrote:
Hi,
Because of the big overhead by locked refcount operations and memory
barriers long strings and dynamic arrays are not thread safe, even
reading needs serializing if the data will be
On 05/12/2014 10:40 AM, Martin Schreiber wrote:
AFAIK memory barriers are extremely evil.
Of course with modern CPUs this is correct.
Anyway, not allowing normal seemingly innocent language types for
ubiquitous use asks for an infinite count of problems.
-Michael
On Monday 12 May 2014 10:57:27 Michael Schnell wrote:
On 05/12/2014 10:40 AM, Martin Schreiber wrote:
AFAIK memory barriers are extremely evil.
Of course with modern CPUs this is correct.
Anyway, not allowing normal seemingly innocent language types for
ubiquitous use asks for an infinite
On 05/12/2014 11:02 AM, Martin Schreiber wrote:
Managed types apparently are not innocent. ;-)
That is obviously for language developers. But to the language users
thy seem to innocent ;-)
-Michael
--
Accelerate Dev
The overhead? Every operation which inc/dec's ref count, for example
That's why me recommend both types - You may implement unsafe types
first and safe ones later.
--
Accelerate Dev Cycles with Automated Cross-Browser
Hi,
Because of the big overhead by locked refcount operations and memory barriers
long strings and dynamic arrays are not thread safe, even reading needs
serializing if the data will be accessed from several threads.
Opinions?
Martin
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:
#149; 3
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
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
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 ?
12 matches
Mail list logo
