<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>When I proposed TInt I had actually forgotten about LONGINT!<div>LONGINT is easier to code to (until/unless we get operator overloading...)</div><div><br></div><div>TInt is easier to extend, and is portable to before the current release.</div><div>I think LONGINT is adequate.</div><div>I did extent TInt to 72 bits I think.</div><div><br></div><div> - Jay<br><br><br><div>> Date: Thu, 4 Jun 2015 09:37:06 -0500<br>> From: rodney_bates@lcwb.coop<br>> To: jay.krell@cornell.edu; hosking@purdue.edu<br>> CC: m3devel@elegosoft.com<br>> Subject: Re: [M3devel] 32bit host 64bit target TextLiteral recurring problem<br>> <br>> <br>> <br>> On 06/03/2015 06:14 PM, Jay K wrote:<br>> > sorry, I missed that it is literals...so I can convert a blueray movie into a source file containing the data all in a text? Far fetched.<br>> > An array of chars? Probably has same problem.<br>> ><br>> ><br>> > Can I/we please LONGINT-ize the compiler now, for all type sizes and field offsets?<br>> ><br>> > - Jay<br>> ><br>> <br>> I'm OK with doing it, but I thought you had been talking about using TInt.<br>> Would that be better? It would be more general. But LONGINT would be<br>> faster at compile time, and less work, since the arithmetic operators<br>> would not need to be changed to TInt function calls. There might<br>> be quite a lot of those I guess the compiler would be of about equal<br>> help in finding missed places to be changed, either way.<br>> <br>> I just checked, and LONGINT is in the release compiler, contrary to<br>> my sense of relative history, so there would be no bootstrap barrier.<br>> <br>> Either would allow a 32-bit hosted compiler (cross- or native-) to handle<br>> types whose byte-count approached 2^31, instead of just 2^23. With a<br>> 64-bit hosted compiler, TInt would handle 2^63 byte-sized objects,<br>> whereas LONGINT would only go to 2^55. Do we really care?<br>> <br>> ><br>> ><br>> > ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------<br>> --<br>> > Subject: Re: [M3devel] 32bit host 64bit target TextLiteral recurring problem<br>> > From: hosking@purdue.edu<br>> > Date: Wed, 3 Jun 2015 14:07:02 -0400<br>> > CC: m3devel@elegosoft.com<br>> > To: jay.krell@cornell.edu<br>> ><br>> > It’s only TEXT /literals/ that are limited here. As in, what appears in a source program.<br>> ><br>> ><br>> -- <br>> Rodney Bates<br>> rodney.m.bates@acm.org<br></div></div> </div></body>
</html>