🚀 go-pugleaf

Eugene Mayevski [SecureBlackbox] wrote:

>Bob Gonder wrote:
>
>>>How to make sure that each and every one of the waiting thread be signalled?
>> You already create the event to not reset, so if you don't reset the
>> event in your thread code, then all threads will get the event signal.
>
>If the event is auto-reset, they will get it either anyway. The 
>difference between semaphore and event is that semaphore awakes one 
>listener and decrements semaphore by 1. And event awakes all listeners 
>and then is reset. So the OP should use semaphores.

Did I read this wrong?
"CreateEvent()
bManualReset
Specifies whether a manual-reset or auto-reset event object is
created. If TRUE, then you must use the ResetEvent function to
manually reset the state to nonsignaled. If FALSE, Windows
automatically resets the state to nonsignaled after a single waiting
thread has been released. "

Sounds like, if TRUE, all threads (and the OP had several waiting on
the same event) will signal, and if FALSE, only One will signal.
Either that, or the Docs are wrong.

Ahh, perhaps you were recommending Named Semaphores so that all
threads in all instances of the program could all release with a
single call?
For that, I suppose he'd need to use WaitMultiple, and the Named
Semaphore would be essentially a Kill Notification (Thread gets it and
self-terminates)  Using the current process-level events for rerunning
the threads. (Or a second local semaphore so he could restart a given
number of threads with one call.)