<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'>
I think that iNTEGER and CARDINAL in general, in the front end (certainly NOT in Modula-3 in general)<br>
should be Target.Int, Target.Cardinal. In general, though not always, target sorts of quantities are being manipulated.<br>
Just that they are usually small.<br>
What happened is I picked out some code at random in the frontend and started converting it to use Int/Cardinal.<br>
The code in particular was what counts up functions in objects and multiplies by size of address to get offset.<br>
It does matter hypothetically, but is a much bigger stretch than other place -- ie. object types with billions of functions.<br>
<br>
- Jay<br><br>> From: hosking@cs.purdue.edu<br>> Date: Wed, 15 Dec 2010 14:41:44 -0500<br>> To: jkrell@elego.de<br>> CC: m3commit@elegosoft.com<br>> Subject: Re: [M3commit] CVS Update: cm3<br>> <br>> Jay, I'm not sure where you are going with all of this TCardinal stuff.<br>> <br>> What is the problem you are trying to solve?<br>> <br>> 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.<br>> <br>> On Dec 15, 2010, at 5:21 PM, Jay Krell wrote:<br>> <br>> > CVSROOT: /usr/cvs<br>> > Changes by: jkrell@birch. 10/12/15 17:21:53<br>> > <br>> > Modified files:<br>> > cm3/m3-sys/m3middle/src/: TCardinal.m3 <br>> > <br>> > Log message:<br>> > use correct comparison function<br>> <br> </body>
</html>