From: Loren J. Rittle <ljrittle@acm.org>
Date: Thu, 15 Nov 2001 09:06:14 +0000 (+0000)
Subject: index.html (Is libstdc++-v3 thread-safe?): Clarify wording.
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=87bc7fa6aab909eb842be0800e0284b0daa3de70;p=platform%2Fupstream%2Fgcc.git

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

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

From-SVN: r47045
---

diff --git a/libstdc++-v3/ChangeLog b/libstdc++-v3/ChangeLog
index 12e7692..3bff900 100644
--- a/libstdc++-v3/ChangeLog
+++ b/libstdc++-v3/ChangeLog
@@ -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>
 
diff --git a/libstdc++-v3/docs/html/faq/index.html b/libstdc++-v3/docs/html/faq/index.html
index 83d678f..e7da17e 100644
--- a/libstdc++-v3/docs/html/faq/index.html
+++ b/libstdc++-v3/docs/html/faq/index.html
@@ -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>