[M3devel] cm3 regression

[Mika Nystrom]

Jay writes:
>--_50e47a65-f79d-472b-8eaf-fbcc30b6410e_
>Content-Type: text/plain; charset="iso-8859-1"
>Content-Transfer-Encoding: quoted-printable
>
>new source -> compiling Cstdlib.i3"..\src\C\32BITS\BasicCtypes.i3", line 18=
>: illegal based LONGINT literal, zero used"..\src\C\32BITS\BasicCtypes.i3",=
> line 18: illegal based LONGINT literal, zero used
>  long_long          =3D [-16_7fffffffffffffffL-1L .. 16_7fffffffffffffffL]=
>;
>=20
>Why isn't this LONGINT? So that NT386 can limp along? And it'd be correct f=
>or the rest, eh?
>I'll try it and see..
>=20
>The underlying system (the compiler) has (U)Int[8,16,32,64]
>They should just be used here imho..
>=20
>Also, what should "long" be on 64bit?
>On Windows it is 32 bits always.
>On 32 bit systems it is 32 bits.
>I think the 64bits directory is going to be forked for AMD64_NT_*.
>The Windows decision imho has successfully been applied to more code and mo=
>re users so therefore is better by practical success, even if the whole iss=
>ue is problematic almost no matter what. Clearly the C and Modula-3 notions=
> of integers are pretty poor..

I have to re-code my program to use Int64 if I want it to use the
natural INTEGER size on 64 bit machines?  No thanks.