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 is this true ?
Of course any language-introduced operation needs to be thread-save ! If library functions are not thread-save this needs decent documentation. Composed Types (records, Objects, problem: complex and int64 on a 32 Bit CU) need to be documented as not being allowed to be considered a being handled in an atomic way, but it should be save to use Strings (as any not obviously composed language objects) in any thread without restriction. OTOH, e.g saying "TList" is not thread save is not clear enough, It should be stated that using multiple instances of TList in multiple threads is save as long as the same instance is not used in multiple threads. OTOH TThreadList is supposed to be thread save even in this use. -Michael ------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs _______________________________________________ mseide-msegui-talk mailing list mseide-msegui-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
