[M3devel] purported condition variable problems on Win32?

[Jay K]

 https://sourceforge.net/p/pthreads4w/code/ci/master/tree/README.CV
 vs.
http://www.cs.wustl.edu/~schmidt/win32-cv-1.html  vs.  https://modula3.elegosoft.com/cgi-bin/cvsweb.cgi/cm3/m3-libs/m3core/src/thread/WIN32/ThreadWin32.m3?rev=1.210.2.1;content-type=text%2Fplain   I wrote this:  PROCEDURE XWait(m: Mutex; c: Condition; act: Activation;                alertable: BOOLEAN) RAISES {Alerted} =  (* LL = m on entry and exit, but not for the duration   * see C:\src\jdk-6u14-ea-src-b05-jrl-23_apr_2009\hotspot\agent\src\os\win32\Monitor.cpp   * NOTE that they merge the user lock and the condition lock.   * http://www.cs.wustl.edu/~schmidt/win32-cv-1.html   *   "3.3. The Generation Count Solution"   *)   
 Do we have the problems described in README.CV?
  I haven't looked through the ACE code to see to what extent they resemble solution 3.3, or if they changed as a result of this discussion -- which I admit I don't understandand haven't read closely.

Spurious wakeups are ok, though should be minimized. 
I'd still rather not drop pre-Vista support but I realize it becomes more interesting as time advances.
  Thank you,  - Jay 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20160705/060aa895/attachment-0002.html>