Added hint to TCL_DECLARE_MUTEX macro usage.

1 files changed, 7 insertions, 3 deletions

diff --git a/doc/Thread.3 b/doc/Thread.3
index f319d7b..ba33882 100644
--- a/doc/Thread.3
+++ b/doc/Thread.3
@@ -5,7 +5,7 @@
 '\" See the file "license.terms" for information on usage and redistribution
 '\" of this file, and for a DISCLAIMER OF ALL WARRANTIES.
 '\" 
-'\" RCS: @(#) $Id: Thread.3,v 1.14.2.1 2004/11/25 15:31:18 vasiljevic Exp $
+'\" RCS: @(#) $Id: Thread.3,v 1.14.2.2 2004/11/25 15:48:52 vasiljevic Exp $
 '\" 
 .so man.macros
 .TH Threads 3 "8.1" Tcl "Tcl Library Procedures"
@@ -140,8 +140,9 @@ creating multithreaded scripts (for example, scripts that could spawn
 a Tcl interpreter in a separate thread).  If you need to add this
 feature at this time, see the \fItclThreadTest.c\fR
 file in the Tcl source distribution for an experimental implementation
-of a Tcl "Thread" package implementing thread creation and management
-commands at the script level.
+or use the Tcl "Threading Extension" package implementing thread creation
+and management commands at the script level.
+
 
 .SH DESCRIPTION
 A mutex is a lock that is used to serialize all threads through a piece
@@ -155,6 +156,9 @@ On some platforms it will result in a deadlock.
 .VE
 The \fBTcl_MutexLock\fR, \fBTcl_MutexUnlock\fR and \fBTcl_MutexFinalize\fR
 procedures are defined as empty macros if not compiling with threads enabled.
+For declaration of mutexes the \fBTCL_DECLARE_MUTEX\fR macro should be used.
+This macro assures correct mutex handling even when the core is compiled
+without threads enabled. 
 .PP
 A condition variable is used as a signaling mechanism:
 a thread can lock a mutex and then wait on a condition variable