From 48d16e09ad7dc9ef461faba277f5075ee71a5826 Mon Sep 17 00:00:00 2001
From: Vadim Zeitlin <vadim@wxwidgets.org>
Date: Wed, 3 Oct 2007 00:13:51 +0000
Subject: [PATCH] semaphore with count of 1 is not exactly the same as mutex

git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@49021 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
---
 docs/latex/wx/semaphor.tex | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/docs/latex/wx/semaphor.tex b/docs/latex/wx/semaphor.tex
index ebf41109ad..9d9271f944 100644
--- a/docs/latex/wx/semaphor.tex
+++ b/docs/latex/wx/semaphor.tex
@@ -47,8 +47,9 @@ No base class
 \func{}{wxSemaphore}{\param{int }{initialcount = 0}, \param{int }{maxcount = 0}}
 
 Specifying a {\it maxcount} of $0$ actually makes wxSemaphore behave as if
-there is no upper limit. If maxcount is $1$, the semaphore behaves exactly as a
-mutex.
+there is no upper limit. If maxcount is $1$, the semaphore behaves almost as a
+mutex (but unlike a mutex it can be released by a thread different from the one
+which acquired it).
 
 {\it initialcount} is the initial value of the semaphore which must be between
 $0$ and {\it maxcount} (if it is not set to $0$).
-- 
2.45.2

