[M3commit] CVS Update: cm3

[Randy Coleburn]

Jay:
 
I haven't studied this code in depth, but on the surface I doubt your change is "correct".  
 
I think the more telling problem is that if you look at the body of WinTrestle.Release, it is empty, save for a comment that it is not yet implemented.  So, it would seem that if WinTrestle.Acquire is called more than once, you will crash because the locks have not been released.
 
Further, I don't think it would make sense to release the locks before calling out to Windows, and then reacquire them upon return.  The locks are known to Modula-3 and not Windows.  Releasing them will allow other competing threads to acquire them while you are in the Windows subsystem and would seem to violate whatever protections were in place per holding the locks.  Upon return from Windows, the thread will be back in competition with others to reacquire the locks it gave up and upon success, there is no guarantee that the other threads didn't disturb the state the original thread depended upon.
 
I would suggest reverting these changes and looking to implement the Release procedure.
 
Regards,
Randy

>>> Jay Krell <jkrell at elego.de> 8/14/2008 4:26 PM >>>
CVSROOT:/usr/cvs
Changes by:jkrell at birch.08/08/14 16:26:59

Modified files:
cm3/m3-ui/ui/src/winvbt/: WinTrestle.m3 

Log message:
release locks when calling out to Win32 to prevent recursive lock acquisition. correct?


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3commit/attachments/20080814/d4ea5647/attachment-0002.html>