X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/b3e51e0f0fea8747bfe4b2a9f9e0d184e4b0db38..5c35d5c1d984f46d33e8181c907936e96160d795:/docs/latex/wx/semaphor.tex?ds=sidebyside diff --git a/docs/latex/wx/semaphor.tex b/docs/latex/wx/semaphor.tex index 88190caa8b..13f8816fd5 100644 --- a/docs/latex/wx/semaphor.tex +++ b/docs/latex/wx/semaphor.tex @@ -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 @@ -60,7 +60,7 @@ Destructor is not virtual, don't use this class polymorphically. \func{wxSemaError }{Post}{\void} Increments the semaphore count and signals one of the waiting -threads in an atomic way. Returns wxSEMA_OVERFLOW if the count +threads in an atomic way. Returns wxSEMA\_OVERFLOW if the count would increase the counter past the maximum. \wxheading{Return value}