O.K., got some time for MutexSemaphore and in the course of writing it, I
corrected the draft for
EventSemaphore as well, including the code sample.
Therefore, here the suggestions/drafts for documenting the two classes
"EventSemaphore" and
"MutexSemaphore":
===
A couple of notes that need to added to the MutexSemaphore section
1) On a single thread, acquire requests nests, so if a thread calls acquire
again while already having obtained the semaphore, it will be not blocked.
It requires an equivalent number of release calls to free up the mutex.
2) If t
On 14.03.2019 18:10, Rick McGuire wrote:
> A couple of notes that need to added to the MutexSemaphore section
>
> 1) On a single thread, acquire requests nests, so if a thread calls acquire
> again while already
> having obtained the semaphore, it will be not blocked. It requires an
> equivalent
