[M3commit] CVS Update: cm3

[Jay K]

Is it really? Thread.Init vs. Thread.InitActivations?

I undid it because I was undoing other stuff but this part seems ok to me.

It is sometimes easier to see relationships by inlining, when one small function calls another, I actually can't see enough on my screen at once (as opposed to the more normal problem of functions being too long to see enough).

 

ThreadBase vs. RunThread there are issues there, I'll leave it as you left it.

 - Jay

 


From: hosking at cs.purdue.edu
To: jkrell at elego.de
Date: Sun, 8 Nov 2009 19:11:30 -0500
CC: m3commit at elegosoft.com
Subject: Re: [M3commit] CVS Update: cm3

Don't do that!  Let the compiler do it if it decides to.  The separation is conceptually important!





Antony Hosking | Associate Professor | Computer Science | Purdue University
305 N. University Street | West Lafayette | IN 47907 | USA
Office +1 765 494 6001 | Mobile +1 765 427 5484



On 8 Nov 2009, at 22:42, Jay Krell wrote:

CVSROOT: /usr/cvs
Changes by: jkrell at birch. 09/11/08 22:42:56

Modified files:
cm3/m3-libs/m3core/src/thread/PTHREAD/: ThreadPThread.m3 

Log message:
inline InitActivations into its only caller Init

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