Amebis/wxWidgets
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Spelling fixes from Andreas Mohr (patch #1360064)

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@36199 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Mart Raudsepp
2005-11-19 01:07:56 +00:00
parent 8b28584104
commit 90e572f1e5
33 changed files with 113 additions and 113 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/latex/wx/semaphor.tex
View File

@@ -20,8 +20,8 @@ decrements the counter. As soon as it reaches $0$, any subsequent calls to
counter becomes strictly positive again as the result of calling
\helpref{Post}{wxsemaphorepost} which increments the counter.
In general, the semaphores are useful to restrict access to a shared resource
which can only be accessed by some fixed number of clients at once. For
In general, semaphores are useful to restrict access to a shared resource
which can only be accessed by some fixed number of clients at the same time. For
example, when modeling a hotel reservation system a semaphore with the counter
equal to the total number of available rooms could be created. Each time a room
is reserved, the semaphore should be acquired by calling
@@ -43,7 +43,7 @@ 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
there is no upper limit. If maxcount is $1$, the semaphore behaves exactly as a
mutex.
{\it initialcount} is the initial value of the semaphore which must be between