[M3commit] CVS Update: cm3

[Jay K]

I think that iNTEGER and CARDINAL in general, in the front end (certainly NOT in Modula-3 in general)

should be Target.Int, Target.Cardinal. In general, though not always, target sorts of quantities are being manipulated.

Just that they are usually small.

What happened is I picked out some code at random in the frontend and started converting it to use Int/Cardinal.

The code in particular was what counts up functions in objects and multiplies by size of address to get offset.

It does matter hypothetically, but is a much bigger stretch than other place -- ie. object types with billions of functions.



 - Jay

> From: hosking at cs.purdue.edu
> Date: Wed, 15 Dec 2010 14:41:44 -0500
> To: jkrell at elego.de
> CC: m3commit at elegosoft.com
> Subject: Re: [M3commit] CVS Update: cm3
> 
> Jay, I'm not sure where you are going with all of this TCardinal stuff.
> 
> What is the problem you are trying to solve?
> 
> The front-end doesn't use CARDINAL anywhere that is problematic for targeting 64-bit from 32-bit, so I don't understand why you will need to model it in any way using this new TCardinal.
> 
> On Dec 15, 2010, at 5:21 PM, Jay Krell wrote:
> 
> > CVSROOT:	/usr/cvs
> > Changes by:	jkrell at birch.	10/12/15 17:21:53
> > 
> > Modified files:
> > 	cm3/m3-sys/m3middle/src/: TCardinal.m3 
> > 
> > Log message:
> > 	use correct comparison function
> 
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3commit/attachments/20101215/1bd5f2e9/attachment-0002.html>