title: When a thread that calls SetWaitableTimer exits while another thread is waiting on the timer, is the timer cancelled?
body: <p><a href="http://msdn.microsoft.com/en-us/library/windows/desktop/ms686289%28v=vs.85%29.aspx" rel="nofollow">http://msdn.microsoft.com/en-us/library/windows/desktop/ms686289%28v=vs.85%29.aspx</a></p>
  
  <p>According to msdn, in the remarks sections, it states:
  "If the thread that set the timer terminates and there is an associated completion routine, the timer is canceled. However, the state of the timer remains unchanged. <strong>If there is no completion routine, then terminating the thread has no effect on the timer.</strong>"</p>
  
  <p>Then further down, it states:
  "<strong>If the thread that called SetWaitableTimer exits, the timer is canceled. This stops the timer before it can be set to the signaled state and cancels outstanding APCs; it does not change the signaled state of the timer.</strong>"</p>
  
  <p>Hence my question, 
  if I have one thread calling SetWaitableTimer without an associated completion routine and another thread calling WaitOnMultipleObjects(passing in the timer object handle) and the thread that calls SetWaitiableTmer exits shortly thereafter, would the timer object be cancelled or would it still become signaled when the period expires?</p>