From 87bc7fa6aab909eb842be0800e0284b0daa3de70 Mon Sep 17 00:00:00 2001 From: "Loren J. Rittle" Date: Thu, 15 Nov 2001 09:06:14 +0000 Subject: [PATCH] index.html (Is libstdc++-v3 thread-safe?): Clarify wording. * docs/html/faq/index.html (Is libstdc++-v3 thread-safe?): Clarify wording. From-SVN: r47045 --- libstdc++-v3/ChangeLog | 5 +++++ 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 12e7692e953..3bff900f5c5 100644 --- a/libstdc++-v3/ChangeLog +++ b/libstdc++-v3/ChangeLog @@ -1,3 +1,8 @@ +2001-11-15 Loren J. Rittle + + * docs/html/faq/index.html (Is libstdc++-v3 thread-safe?): Clarify + wording. + 2001-11-15 Loren J. Rittle diff --git a/libstdc++-v3/docs/html/faq/index.html b/libstdc++-v3/docs/html/faq/index.html index 83d678f76a5..e7da17e3083 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

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.

See chapters 17 (library introduction), 23 -- 2.30.2