[M3commit] CVS Update: cm3

[Jay K]

Putting them elsewhere violates the opacity.

Not using this code in m3back would require duplication.

m3back does recieve plenty of Target.Int parameters, and already uses TInt and maybe TWord, and TFloat.

Hard to deal with the opaque parameters unless TInt is available...

 

 - Jay
 


From: hosking at cs.purdue.edu
Date: Mon, 18 Jan 2010 09:11:02 -0500
To: jkrell at elego.de
CC: m3commit at elegosoft.com
Subject: Re: [M3commit] CVS Update: cm3

Jay,


m3middle is intended for m3front as the client.
Not m3back.  If you need all these constants you should put them somewhere in m3back.




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



On 18 Jan 2010, at 14:28, Jay Krell wrote:

CVSROOT: /usr/cvs
Changes by: jkrell at birch. 10/01/18 14:28:43

Modified files:
cm3/m3-sys/m3middle/src/: TInt.i3 

Log message:
add more constants for m3back; restore more verbose form that makes it easier to see these are arrays of bytes

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