Commit 87bc7fa6 by Loren J. Rittle Committed by Loren J. Rittle

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

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

From-SVN: r47045
parent 2a692463
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> 2001-11-15 <bjornw@planetarion.com>
Loren J. Rittle <ljrittle@acm.org> Loren J. Rittle <ljrittle@acm.org>
......
...@@ -783,9 +783,11 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff ...@@ -783,9 +783,11 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff
</p> </p>
<p>All library objects are safe to use in a multithreaded program as <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 long as each thread carefully locks out access by any other thread
while it uses any object visible to another thread. This requirement while it uses any object visible to another thread. In general,
includes both read and write access to objects; do not assume that this requirement includes both read and write access to objects;
two threads may read a shared standard container at the same time. unless otherwise documented as safe, do not assume that two
threads may access a shared standard library object at the
same time.
</p> </p>
<p>See chapters <a href="../17_intro/howto.html#3">17</a> (library <p>See chapters <a href="../17_intro/howto.html#3">17</a> (library
introduction), <a href="../23_containers/howto.html#3">23</a> introduction), <a href="../23_containers/howto.html#3">23</a>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment