On 11.04.2019 18:30, Rony G. Flatscher wrote:
>
> This posting was meant to define the documentation for the new Rexx classes
> EventSemaphore and
> MutexSemaphore.
>
> Just wanted to make sure that it does not get lost, hence the question
> whether I should submit it
> as some form of a patch?
>
This posting was meant to define the documentation for the new Rexx classes
EventSemaphore and
MutexSemaphore.
Just wanted to make sure that it does not get lost, hence the question whether
I should submit it as
some form of a patch?
Also, if I know into which XML-file to place it, I could try
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
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
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":
===
