diff options
| -rw-r--r-- | libstdc++-v3/ChangeLog | 5 | ||||
| -rw-r--r-- | libstdc++-v3/docs/html/faq/index.html | 8 |
2 files changed, 10 insertions, 3 deletions
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> |