OpenE2K
/
gcc
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

index.html (Is libstdc++-v3 thread-safe?): Clarify wording. 

* docs/html/faq/index.html (Is libstdc++-v3 thread-safe?): Clarify
        wording.

From-SVN: r47045
This commit is contained in:
Loren J. Rittle 2001-11-15 09:06:14 +00:00 committed by Loren J. Rittle
parent 2a692463e5
commit 87bc7fa6aa
2 changed files with 10 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
libstdc++-v3/ChangeLog
View File

@ -1,3 +1,8 @@
2001-11-15 Loren J. Rittle <ljrittle@acm.org>
* docs/html/faq/index.html (Is libstdc++-v3 thread-safe?): Clarify
wording.
2001-11-15 <bjornw@planetarion.com>
Loren J. Rittle <ljrittle@acm.org>

8
libstdc++-v3/docs/html/faq/index.html
View File

@ -783,9 +783,11 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff
</p>
<p>All library objects are safe to use in a multithreaded program as
long as each thread carefully locks out access by any other thread
while it uses any object visible to another thread. This requirement
includes both read and write access to objects; do not assume that
two threads may read a shared standard container at the same time.
while it uses any object visible to another thread. In general,
this requirement includes both read and write access to objects;
unless otherwise documented as safe, do not assume that two
threads may access a shared standard library object at the
same time.
</p>
<p>See chapters <a href="../17_intro/howto.html#3">17</a> (library
introduction), <a href="../23_containers/howto.html#3">23</a>