summaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorvasiljevic <zv@archiware.com>2004-11-25 16:01:16 (GMT)
committervasiljevic <zv@archiware.com>2004-11-25 16:01:16 (GMT)
commitc777c673b8cd6683cf7969c086d8bc6a0dee3785 (patch)
tree19b53ffd03834dce742b406b4a65687ce8bb42c1 /doc
parentcc7246b86407186366a64a86fa18704965629271 (diff)
downloadtcl-c777c673b8cd6683cf7969c086d8bc6a0dee3785.zip
tcl-c777c673b8cd6683cf7969c086d8bc6a0dee3785.tar.gz
tcl-c777c673b8cd6683cf7969c086d8bc6a0dee3785.tar.bz2
Added changes from core-8-4-branch
Diffstat (limited to 'doc')
-rw-r--r--doc/Notifier.34
-rw-r--r--doc/Thread.35
2 files changed, 6 insertions, 3 deletions
diff --git a/doc/Notifier.3 b/doc/Notifier.3
index 3bf7c0f..6bb31af 100644
--- a/doc/Notifier.3
+++ b/doc/Notifier.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: Notifier.3,v 1.12 2004/10/07 16:05:14 dkf Exp $
+'\" RCS: @(#) $Id: Notifier.3,v 1.13 2004/11/25 16:01:16 vasiljevic Exp $
'\"
.so man.macros
.TH Notifier 3 8.1 Tcl "Tcl Library Procedures"
@@ -33,7 +33,7 @@ void
\fBTcl_ThreadQueueEvent\fR(\fIthreadId, evPtr, position\fR)
.sp
void
-\fBTcl_ThreadAlert\fR(\fIthreadId, clientData\fR)
+\fBTcl_ThreadAlert\fR(\fIthreadId\fR)
.sp
Tcl_ThreadId
\fBTcl_GetCurrentThread\fR()
diff --git a/doc/Thread.3 b/doc/Thread.3
index d1962e4..0192588 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.19 2004/10/07 14:44:35 dkf Exp $
+'\" RCS: @(#) $Id: Thread.3,v 1.20 2004/11/25 16:01:17 vasiljevic Exp $
'\"
.so man.macros
.TH Threads 3 "8.1" Tcl "Tcl Library Procedures"
@@ -145,6 +145,9 @@ The result of locking a mutex twice from the same thread is undefined.
On some platforms it will result in a deadlock.
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