This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
PATCH: clarify FAQ wording
- From: Loren James Rittle <rittle at latour dot rsch dot comm dot mot dot com>
- To: libstdc++ at gcc dot gnu dot org
- Date: Thu, 15 Nov 2001 03:08:58 -0600 (CST)
- Subject: PATCH: clarify FAQ wording
- Reply-to: rittle at labs dot mot dot com
This proposed word change was previously posted. The person with the
further questions about the section agreed it was better. Installed
on mainline.
* docs/html/faq/index.html (Is libstdc++-v3 thread-safe?): Clarify
wording.
(index.html not updated for this minor change since I still don't have
lnyx installed.)
Index: docs/html/faq/index.html
===================================================================
RCS file: /cvs/gcc/egcs/libstdc++-v3/docs/html/faq/index.html,v
retrieving revision 1.25
diff -c -r1.25 index.html
*** index.html 2001/11/07 21:08:53 1.25
--- index.html 2001/11/15 08:56:59
***************
*** 783,791 ****
</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.
</p>
<p>See chapters <a href="../17_intro/howto.html#3">17</a> (library
introduction), <a href="../23_containers/howto.html#3">23</a>
--- 783,793 ----
</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. 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>