<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style>
</head>
<body class='hmmessage'>
I at least did move the hacks to one place.<BR>
I agree it isn't nice.<BR>
This is due to my changes, not yours -- changing File.T.status().size to LONGINT.<BR>
There's no way to use that in the "compiler" and still support old compiler/libm3, right?<BR>
Ok now that I centralized it to sysutils?<BR>
<BR>
<BR>
Leave status() alone as using INTEGER and introduce statusL()?<BR>
<BR>
<BR>
Or leave size alone and introduce sizeL?<BR>
That's not a complete solution because you have to set size to something.<BR>
-1 if it doesn't fit?<BR>
<BR>
<BR>
Or just get past the bootstrapping and put it back using VAL?<BR>
It seems a tough situation..the compiler is otherwise I believe<BR>
very compatible with old compiler/libm3.<BR>
<BR>
<BR>
- Jay<BR><BR> <BR>> From: hosking@cs.purdue.edu<BR>> Date: Fri, 15 Jan 2010 10:13:06 -0500<BR>> To: jkrell@elego.de<BR>> CC: m3commit@elegosoft.com<BR>> Subject: Re: [M3commit] CVS Update: cm3<BR>> <BR>> Jay, all of these changes seem unnecessary (and worse, clutter the source with a variety of hacks). I had no problem building against both versions of m3core and libm3 in order to bootstrap a new compiler. What is going on here?<BR>> <BR>> On 15 Jan 2010, at 14:41, Jay Krell wrote:<BR>> <BR>> > CVSROOT: /usr/cvs<BR>> > Changes by: jkrell@birch. 10/01/15 14:41:00<BR>> > <BR>> > Modified files:<BR>> > cm3/m3-sys/m3quake/src/: QCompiler.m3 QScanner.i3 QScanner.m3 <BR>> > m3makefile <BR>> > Added files:<BR>> > cm3/m3-sys/m3quake/src/: QScannerC.c <BR>> > <BR>> > Log message:<BR>> > m3quake also can't use libm3 File.T.status().size and be compatible<BR>> > with both old and new libm3 (INTEGER vs. LONGINT)<BR>> <BR> </body>
</html>