From b86ee4a56ded8c3a4090f7eff5b3efd0f95e4bde Mon Sep 17 00:00:00 2001 From: "Loren J. Rittle" Date: Wed, 30 May 2001 08:30:04 +0000 Subject: howto.html: Update link. * docs/html/17_intro/howto.html: Update link. * docs/html/23_containers/howto.html: Likewise. Add new link. From-SVN: r42703 --- libstdc++-v3/docs/html/17_intro/howto.html | 8 ++++---- libstdc++-v3/docs/html/23_containers/howto.html | 17 ++++++++++------- 2 files changed, 14 insertions(+), 11 deletions(-) (limited to 'libstdc++-v3/docs/html') diff --git a/libstdc++-v3/docs/html/17_intro/howto.html b/libstdc++-v3/docs/html/17_intro/howto.html index ae568d4..ee918c5 100644 --- a/libstdc++-v3/docs/html/17_intro/howto.html +++ b/libstdc++-v3/docs/html/17_intro/howto.html @@ -8,7 +8,7 @@ libstdc++-v3 HOWTO: Chapter 17 - + @@ -56,7 +56,7 @@ and gcc mailing lists on a regular basis (probably by a cron job). This entry will mention a very little bit about the general MT issues with libstdc++. The latest status and quick notes will be - in FAQ 5.6. Some discussion about threadsafe containers will be + in FAQ 5.6. Some discussion about thread-safe containers will be in section 6.8 (the HOWTOs on containers).

The libstdc++ code (all of it, not just the containers) has been @@ -65,7 +65,7 @@ portable to all platforms. A minor problem that pops up every so often is different interpretations of what "thread-safe" means for a library (not a general program). We currently use the - same + same definition that SGI uses for their STL subset.

A recent journal article has described "atomic integer @@ -145,7 +145,7 @@

Comments and suggestions are welcome, and may be sent to the mailing list. -
$Id: howto.html,v 1.1 2000/12/10 04:03:09 pme Exp $ +
$Id: howto.html,v 1.2 2001/04/03 00:26:54 pme Exp $

diff --git a/libstdc++-v3/docs/html/23_containers/howto.html b/libstdc++-v3/docs/html/23_containers/howto.html index c8350a7..f9d0431 100644 --- a/libstdc++-v3/docs/html/23_containers/howto.html +++ b/libstdc++-v3/docs/html/23_containers/howto.html @@ -8,7 +8,7 @@ libstdc++-v3 HOWTO: Chapter 23 - + @@ -189,13 +189,16 @@ aspects of multithreading (e.g., the library as a whole), see the Received Wisdom on Chapter 17.

-

An excellent page to read when working with templatized containers - and threads is - SGI's - http://www.sgi.com/Technology/STL/thread_safety.html. The +

Two excellent pages to read when working with templatized containers + and threads are + SGI's + http://www.sgi.com/tech/stl/thread_safety.html and + SGI's + http://www.sgi.com/tech/stl/Allocators.html. The libstdc++-v3 uses the same definition of thread safety when discussing design. A key point that beginners may miss is the - fourth major paragraph ("For most clients,"...), pointing + fourth major paragraph of the first page mentioned above + ("For most clients,"...), pointing out that locking must nearly always be done outside the container, by client code (that'd be you, not us *grin*).

@@ -236,7 +239,7 @@

Comments and suggestions are welcome, and may be sent to the mailing list. -
$Id: howto.html,v 1.1 2000/12/10 04:04:55 pme Exp $ +
$Id: howto.html,v 1.2 2001/04/03 00:26:55 pme Exp $

-- cgit v1.1