About my SemaMonitor 2.02...

[Ramine]

Hello.....


About my SemaMonitor 2.02...

When you use Semaphores , and when you release and you have attainef the
maximum count to be released, the signal(or the release) will be lost
and this is no good, this is why i have implemented my new algorithm of
my SemaMonitor version 2.02, now if you want the signal(s) to not be
lost with my SemaMonitor, you can configure it by passing a parameter to
the constructor, and it works great, this has helped to implement my
Concurrent FIFO Queue 1 and my Concurrent FIFO queue 2 without using
Condition variables.


You can download the concurrent FIFO queues from:


https://sites.google.com/site/aminer68/concurrent-fifo-queue-1

and from:

https://sites.google.com/site/aminer68/concurrent-fifo-queue-2


And you can download my Lightweight SemaMonitor and my SemaCondvar
version 2.02 from:

Lightweight SemaCondvar & SemaMonitor version 2.02

https://sites.google.com/site/aminer68/light-weight-semacondvar-semamonitor

And:

SemaCondvar & SemaMonitor version 2.02

https://sites.google.com/site/aminer68/semacondvar-semamonitor


And you can download my C++ synchronization objects library that comes
with my SemaMonitor from:

https://sites.google.com/site/aminer68/c-synchronization-objects-library

Thank you,
Amine Moulay Ramdane.

[Ramine]

On 1/7/2017 6:45 PM, Ramine wrote:
> Hello.....
>
>
> About my SemaMonitor 2.02...
>
> When you use Semaphores , and when you release and you have attainef the

I mean: attained, not attainef