[M3commit] [M3devel] LONGINT used by m3quake/cm3 packages

[Jay K]

I'm able to bootstrap the current system from pre-LONGINT using upgrade.py.
I'm not sure, but our regular builds might do that.
Not so now though.
I think you might be saying however that such a compiler might have bugs in it?
 
 - Jay



________________________________
> From: hosking at cs.purdue.edu
> Date: Fri, 15 Jan 2010 17:50:17 -0500
> To: jay.krell at cornell.edu
> CC: m3devel at elegosoft.com; m3commit at elegosoft.com
> Subject: Re: [M3devel] LONGINT used by m3quake/cm3 packages
>
>
>
> On 15 Jan 2010, at 16:56, Jay K wrote:
>
> VAL(LONGINT, INTEGER) is fine outside of cm3/m3quake,
> but I think what I had is the way to go.
> The bootstrapping pain is otherwise novel.
>
> The bootstrapping pain is now no more novel than when LONGINT was first introduced...
>
> The compiler doesn't otherwise use LONGINT.
> (My doing that it started using it.)
> It ought not until after the current release?
>
> ... so it is pointless trying to build new libraries with an old compiler because the old compiler is built to compile files against old libraries.
>
>
>
> - Jay
>
>
>> Date: Fri, 15 Jan 2010 22:51:15 +0000
>> To: m3commit at elegosoft.com
>> From: hosking at elego.de
>> Subject: [M3commit] CVS Update: cm3
>>
>> CVSROOT: /usr/cvs
>> Changes by: hosking at birch. 10/01/15 22:51:15
>>
>> Modified files:
>> cm3/m3-sys/m3quake/src/: QCompiler.m3 QScanner.i3 QScanner.m3
>>
>> Log message:
>> Revert to VAL.
>>
>