[M3devel] joinMu vs. t.join?

[Jay K]

Oh I think I understand. Global locks really bother me..

 

 - Jay

 


From: hosking at cs.purdue.edu
To: jay.krell at cornell.edu
Date: Sun, 8 Nov 2009 19:00:26 -0500
CC: m3devel at elegosoft.com
Subject: Re: [M3devel] joinMu vs. t.join?





Because the mutex has disappeared into the untraced Activation.  I suppose I could have Thread.T also extend MUTEX to permit it, but it's overkill to do so.  How much contention  would we expect from threads all joining at exactly the same time?  An alternative is to implement Join natively rather than in the Modula-3 space.


On 8 Nov 2009, at 16:35, Jay K wrote:

Tony, why the global joinMu instead of per thread t.join?
 
 - Jay






 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20091109/a524b141/attachment-0002.html>