AuroraMiddleware/scuffed-code
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

ICU-72 Documentation update

Browse Source 
X-SVN-Rev: 136
This commit is contained in:
Helena Chapman 1999-10-28 18:06:45 +00:00
parent 49ec74e4fb
commit 74b9492479
1 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
icu4c/docs/mutex.html
View File

@ -57,6 +57,18 @@ necessary, however time spent inside the mutex is then minimized. </p>
<p>Developers implementing the Mutex are not required to provide reentrant-safe <p>Developers implementing the Mutex are not required to provide reentrant-safe
implementations. </p> implementations. </p>
<h3>Using collators in multi-threaded environment</h3>
<p>Instances of Collator class are meant to be used on per thread basis. Although it is
possible to have multiple threads access one Collator there is no guarante that such a
construct will work, especially if number of threads grows over 10. There are no
limitations on number of threads if each thread creates its own separate instance of
Collator class.</p>
<p>Test results have shown that case with 50 threads accessing 1 collator fails with a
crash after 20 threads are reached. However, a test with 50 threads creating separate
instances works well.</p>
<h3>Implementations</h3> <h3>Implementations</h3>
<p>On Win32 platforms, a reentrant mutex is most naturally implemented on top of a <p>On Win32 platforms, a reentrant mutex is most naturally implemented on top of a