[M3commit] CVS Update: cm3
Tony Hosking
hosking at cs.purdue.edu
Mon Nov 9 01:45:13 CET 2009
You have no guarantee there is no race anyway, since there is no
synchronization to let you see the real state of things.
On 8 Nov 2009, at 19:41, Jay K wrote:
> The repeated assertions somewhat ensure there was no race. Ok with
> removing them.
>
> - Jay
>
>
> > Date: Mon, 9 Nov 2009 01:36:41 +0000
> > To: m3commit at elegosoft.com
> > From: hosking at elego.de
> > Subject: [M3commit] CVS Update: cm3
> >
> > CVSROOT: /usr/cvs
> > Changes by: hosking at birch. 09/11/09 01:36:41
> >
> > Modified files:
> > cm3/m3-libs/m3core/src/thread/PTHREAD/: ThreadPThread.m3
> >
> > Log message:
> > OK, fine, yes we don't need to lock in InitActivations.
> > But why bother with the repeated assertions.
> >
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3commit/attachments/20091108/c1ccbbf0/attachment-0002.html>
More information about the M3commit
mailing list