Re: WaitForMultipleObjects
Chizl <Chizl@NoShitMail.com> wrote:
When I say triggered or fired, they're terms I've always heard and
used for events, I'm speaking of signaled.
Fired an Event
Triggered an Event
Signaled an Event
You see, "event" is really a bad name for Windows event synchronization
object. When most people think of events, they envision something like
VB events or JavaScript events: the user clicks a button, event fires,
some piece of code attached to the event executes. Event synchronization
object doesn't work this way: when you call SetEvent, it just becomes
signalled (if it wasn't already) - it doesn't make any code run in and
of itself, unless some thread was sitting there waiting for the object
to become signalled.
That's why I feel verbs like "fire" and "trigger" are inappropriate for
event synchronization object: they strongly suggest
click-the-button-run-some-code kind of event, which is highly
misleading.
--
With best wishes,
Igor Tandetnik
With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going to
land, and it could be dangerous sitting under them as they fly
overhead. -- RFC 1925